Triple
T20507363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Falls of the Missouri |
E503468
|
entity |
| Predicate | numberOfMajorFalls |
P140355
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Great Falls of the Missouri, numberOfMajorFalls, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfMajorFalls Context triple: [Great Falls of the Missouri, numberOfMajorFalls, 5]
-
A.
numberOfIndividualFalls
Indicates the count of separate falling incidents experienced by an individual.
-
B.
approximateHeightOfFallsViewed
Indicates the estimated vertical height of the waterfalls as observed or perceived by the viewer.
-
C.
heightAboveFalls
Indicates that one entity is located at a higher elevation than a waterfall or waterfalls associated with another entity.
-
D.
fallsFrom
Indicates that one entity moves downward or drops starting from the location or position of another entity.
-
E.
hadMajorRockfall
Indicates that a significant rockfall event has occurred at or affected the subject entity.
- F. None of above. chosen
Provenance (4 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_69e0b4b1e52c8190894281cf7e3283ab |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69dc82dd0819085d64d65a1e72c70 |
completed | April 20, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:36 a.m.