Triple
T24769662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Achagua |
E619684
|
entity |
| Predicate | usesWaterwaysFor |
P83955
|
FINISHED |
| Object | transportation |
—
|
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: transportation | Statement: [Achagua, usesWaterwaysFor, transportation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesWaterwaysFor Context triple: [Achagua, usesWaterwaysFor, transportation]
-
A.
usedWaterway
chosen
Indicates that one entity traveled, transported goods, or otherwise moved via a particular waterway as the route or medium of use.
-
B.
associatedWithWaterways
Indicates a relationship in which something is connected, linked, or relevant to waterways such as rivers, canals, or streams.
-
C.
transportsWaterTo
Indicates that one entity carries or conveys water from its location or source to another entity or destination.
-
D.
waterwayThrough
Indicates that a waterway (such as a river or canal) passes through or traverses a specified geographic area or feature.
-
E.
primaryWaterways
Indicates that the related entities are connected through major or principal bodies of water, such as main rivers, canals, or shipping routes that serve as key waterways 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_69e2fabd04488190a2d13c97be745a2d |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a8dc8081909e2f4b65485a6786 |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:29 a.m.