Triple
T25117061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inga Falls |
E629156
|
entity |
| Predicate | rankedByFlow |
P7476
|
FINISHED |
| Object | one of the largest waterfalls in the world by discharge |
—
|
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 largest waterfalls in the world by discharge | Statement: [Inga Falls, rankedByFlow, one of the largest waterfalls in the world by discharge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankedByFlow Context triple: [Inga Falls, rankedByFlow, one of the largest waterfalls in the world by discharge]
-
A.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
-
B.
rankedAs
Indicates that one entity is assigned a specific position or level in an ordered ranking relative to others.
-
C.
rankingBasis
chosen
Indicates the criterion or standard used to determine the order or rank of entities in a ranking.
-
D.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
E.
rankingType
Indicates the specific basis or method by which items are ordered or ranked relative to one 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f465c7b88c81909fefbf647d1b810d |
completed | May 1, 2026, 8:35 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:27 a.m.