Triple
T28389087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Natural Bridges |
E719100
|
entity |
| Predicate | approximateHeightRange |
P38193
|
FINISHED |
| Object | 200–300 metres |
—
|
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: 200–300 metres | Statement: [Three Natural Bridges, approximateHeightRange, 200–300 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateHeightRange Context triple: [Three Natural Bridges, approximateHeightRange, 200–300 metres]
-
A.
approximateMaximumHeight
Indicates the estimated upper limit of an entity’s height, rather than an exact measured value.
-
B.
heightEstimate
chosen
Indicates an estimated or approximate value for the height of an entity, rather than a precisely measured height.
-
C.
shoulderHeightRange
Indicates the range of vertical height measured from the ground to an entity’s shoulders.
-
D.
averageHeightRange
Indicates the typical minimum and maximum height values that characterize the usual height span associated with an entity or group.
-
E.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: April 28, 2026, 1:12 a.m.