Triple
T26505290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agura Waterfalls |
E669526
|
entity |
| Predicate | hasTypeOfWaterfall |
P36915
|
FINISHED |
| Object | cascade waterfall |
—
|
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: cascade waterfall | Statement: [Agura Waterfalls, hasTypeOfWaterfall, cascade waterfall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfWaterfall Context triple: [Agura Waterfalls, hasTypeOfWaterfall, cascade waterfall]
-
A.
typeOfWaterfall
chosen
Indicates that one entity is a specific kind or category of waterfall in relation to another entity.
-
B.
hasWaterfallType
Indicates that one entity is characterized by or associated with a specific type or classification of waterfall.
-
C.
hasWaterfall
Indicates that one entity possesses, contains, or features a waterfall associated with it.
-
D.
hasNumberOfWaterfalls
Indicates the quantity of waterfalls associated with a given entity.
-
E.
hasWatercourseType
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 27, 2026, 1:16 a.m.