Triple
T11089644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landscape Arch |
E262216
|
entity |
| Predicate | approximateSpanLength |
P25800
|
FINISHED |
| Object | about 88 meters |
—
|
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: about 88 meters | Statement: [Landscape Arch, approximateSpanLength, about 88 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateSpanLength Context triple: [Landscape Arch, approximateSpanLength, about 88 meters]
-
A.
approximateLengthInMeters
chosen
Indicates the estimated or roughly measured length of something expressed in meters.
-
B.
navigationSpanLength
Indicates the distance or extent covered by a navigation segment or span within a route or path.
-
C.
approximateBlockLength
Indicates that one entity specifies or estimates the length of a block in an approximate or non-exact manner.
-
D.
largestSpan
Indicates that the referenced entity has the greatest extent or coverage (in distance, time, or range) among a set of comparable spans.
-
E.
approximateCourseLength
Indicates an estimated or rough value for the length or duration of a course rather than an exact measurement.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799e96ca08190838c8a04d1eb2a16 |
completed | April 9, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.