Triple
T33958234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iraqi national transport network |
E870638
|
entity |
| Predicate | waterwayNode |
P2432
|
FINISHED |
| Object | Tigris River |
—
|
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: Tigris River | Statement: [Iraqi national transport network, waterwayNode, Tigris River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterwayNode Context triple: [Iraqi national transport network, waterwayNode, Tigris River]
-
A.
waterwayContext
Indicates that one entity is a waterway whose characteristics, usage, or significance are defined or influenced by its surrounding geographic or environmental context.
-
B.
waterwayJunction
Indicates a point where two or more waterways meet, intersect, or branch from one another.
-
C.
waterwayLinkBetween
Indicates a connection or linkage between two waterways, such as rivers, canals, or channels, through which water can flow or navigation can occur.
-
D.
waterwaySystem
chosen
Indicates that one entity is part of, or belongs to, a connected network of waterways associated with another entity.
-
E.
waterwayClass
Indicates the classification or type of a waterway based on its navigational, functional, or physical characteristics.
- 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_69f3499c2d7481909c953a5010227725 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: May 1, 2026, 1:49 a.m.