Triple
T21418703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tugela Falls |
E528374
|
entity |
| Predicate | rankAmongWorldsTallestWaterfalls |
P2472
|
FINISHED |
| Object | one of the tallest waterfalls 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 tallest waterfalls in the world | Statement: [Tugela Falls, rankAmongWorldsTallestWaterfalls, one of the tallest waterfalls in the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankAmongWorldsTallestWaterfalls Context triple: [Tugela Falls, rankAmongWorldsTallestWaterfalls, one of the tallest waterfalls in the world]
-
A.
majorWaterfall
Indicates that a waterfall is of significant size, height, or volume relative to other waterfalls.
-
B.
waterfallHeight
Indicates the vertical distance or drop in elevation from the top to the bottom of a waterfall.
-
C.
waterfallName
Indicates that an entity is identified by or associated with the specific name of a waterfall.
-
D.
hasNumberOfWaterfalls
Indicates the quantity of waterfalls associated with a given entity.
-
E.
rankByHeightWorld
chosen
Indicates an ordering of entities based on their relative height compared to all others in the world.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee62d29f948190b820c92014d1c53a |
completed | April 26, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:47 p.m.