Triple
T26290254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Lao Navy |
E661249
|
entity |
| Predicate | notableWaterway |
P187274
|
FINISHED |
| Object | Mekong 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: Mekong River | Statement: [Royal Lao Navy, notableWaterway, Mekong River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWaterway Context triple: [Royal Lao Navy, notableWaterway, Mekong River]
-
A.
keyWaterway
chosen
Indicates that one entity serves as a primary or defining waterway associated with another entity.
-
B.
stateWaterway
Indicates that a waterway is located within, passes through, or is otherwise geographically associated with a particular state.
-
C.
waterwaySystem
Indicates that one entity is part of, or belongs to, a connected network of waterways associated with another entity.
-
D.
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.
-
E.
namedWaterBody
Indicates that an entity is identified as a specific water body by a given name.
- 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_69ee812bbd448190be4d7478b057990a |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fe86cad5108190b0164b8bc6fc23ea |
completed | May 9, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69fe83c0c9888190b6fc40c7f727b569 |
completed | May 9, 2026, 12:45 a.m. |
Created at: April 26, 2026, 10:08 p.m.