Triple
T8876055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsiribihina River |
E211285
|
entity |
| Predicate | transportUse |
P1379
|
FINISHED |
| Object | local river transport |
—
|
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: local river transport | Statement: [Tsiribihina River, transportUse, local river transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportUse Context triple: [Tsiribihina River, transportUse, local river transport]
-
A.
transportationFunction
Indicates that one entity serves to move or carry another entity from one place to another.
-
B.
transportAdvisory
Indicates that guidance, warnings, or recommendations are being issued regarding transportation conditions, operations, or usage.
-
C.
transportType
chosen
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
D.
transportIndependenceGoal
Indicates a goal or intention for an entity to achieve independence from a particular mode, provider, or system of transportation.
-
E.
transportAssumption
Indicates an assumption that something can be transported or carried from one place or context to another.
- 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_69ca838e78748190934d82db3104f855 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc614565788190aa14535760df88c8 |
completed | April 1, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2956788190a311c647b4da17a6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:52 p.m.