Triple
T35597755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samaro Tehsil |
E1028680
|
entity |
| Predicate | locatedInSouthOf |
P161618
|
FINISHED |
| Object | Pakistan |
E1646
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Pakistan | Statement: [Samaro Tehsil, locatedInSouthOf, Pakistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInSouthOf Context triple: [Samaro Tehsil, locatedInSouthOf, Pakistan]
-
A.
locatedSouthOf
Indicates that one entity is positioned geographically to the south of another entity.
-
B.
locatedInCountrySouth
Indicates that the subject entity is geographically situated within a country that lies in the southern part of the world or a specified southern region.
-
C.
locatedSouthWestOf
Indicates that one entity is positioned to the southwest of another entity, combining both a southern and western relative location.
-
D.
locatedInTheSouthernPartOf
chosen
Indicates that one entity is situated within the southern portion or region of another entity.
-
E.
liesSoutheastOf
Indicates that one entity is located to the southeast of another, combining both a southern and eastern directional relationship.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38684251008190a622ac3da34438ef |
completed | June 21, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.