Triple
T23756032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India–Iran Chabahar Agreement |
E587117
|
entity |
| Predicate | aimsToConnect |
P99111
|
FINISHED |
| Object | India |
—
|
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: India | Statement: [India–Iran Chabahar Agreement, aimsToConnect, India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimsToConnect Context triple: [India–Iran Chabahar Agreement, aimsToConnect, India]
-
A.
aimedToConnect
chosen
Indicates an intention or effort by one entity to establish a link, relationship, or communication channel with another entity.
-
B.
connectionTo
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
C.
aimsToCapture
Indicates an intention or effort by one entity to take control of, seize, or gain possession of another entity.
-
D.
aimsToModel
Indicates that one entity is intended or designed to represent, simulate, or approximate the behavior, structure, or properties of another entity.
-
E.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
- 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.