Triple
T1563642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indus River delta |
E33382
|
entity |
| Predicate | hasChannelType |
P8080
|
FINISHED |
| Object | distributary channels |
—
|
LITERAL 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: distributary channels | Statement: [Indus River delta, hasChannelType, distributary channels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChannelType Context triple: [Indus River delta, hasChannelType, distributary channels]
-
A.
hasChannel
chosen
Indicates that one entity possesses, provides, or is associated with a particular communication or distribution channel.
-
B.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
C.
hasQueueType
Indicates that an entity is associated with a specific type or category of queue.
-
D.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
-
E.
hasRouteType
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
- 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_69a885ef9cf48190b0af0f5ce3d02231 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90fccd4b48190a44012888a00af7f |
completed | March 5, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69a907b872f0819096b3df6ad502c63e |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.