Triple
T790193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amazon River |
E16895
|
entity |
| Predicate | lengthRank |
P18229
|
FINISHED |
| Object | one of the longest rivers in the world |
—
|
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: one of the longest rivers in the world | Statement: [Amazon River, lengthRank, one of the longest rivers in the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lengthRank Context triple: [Amazon River, lengthRank, one of the longest rivers in the world]
-
A.
depthRank
Indicates the relative ordering of entities based on how deep or distant they are along a specified depth dimension or hierarchy.
-
B.
rankByLength
chosen
Indicates ordering a set of items based on their length, typically from shortest to longest or vice versa.
-
C.
rankRange
Indicates that an entity’s rank falls within a specified minimum and maximum range.
-
D.
rankIndicated
Indicates that one entity specifies, denotes, or reveals the hierarchical rank or level of another entity.
-
E.
hasRankOrder
Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a7841b0c8190859ecd247e32c6ec |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a50ef72c819084ffe9f31dbd0262 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:38 p.m.