Triple
T23756025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India–Iran Chabahar Agreement |
E587117
|
entity |
| Predicate | relatesToLocation |
P15985
|
FINISHED |
| Object | Chabahar Port |
—
|
NE NERFINISHED |
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: Chabahar Port | Statement: [India–Iran Chabahar Agreement, relatesToLocation, Chabahar Port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatesToLocation Context triple: [India–Iran Chabahar Agreement, relatesToLocation, Chabahar Port]
-
A.
refersToLocation
chosen
Indicates that one entity designates, points to, or identifies a specific location associated with it.
-
B.
relatedPlace
Indicates a relationship where one place is connected or associated with another place in a relevant or meaningful way.
-
C.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
-
D.
connectsLocation
Indicates a relationship where one entity serves as a link or route that joins or provides access between two locations.
-
E.
linkedLocation
Indicates that one location is associated or connected to another location in a meaningful way, such as being related, referenced, or contextually tied.
- F. None of above.
Provenance (3 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_69e2490a0eec81908cdef8a862828d7a |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bdac7b34819086293d161245c529 |
completed | April 29, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:14 p.m.