Triple

T11032302
Position Surface form Disambiguated ID Type / Status
Subject Skyline Arch E260785 entity
Predicate hasApproximateSpan P20336 FINISHED
Object about 21 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 21 meters | Statement: [Skyline Arch, hasApproximateSpan, about 21 meters]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasApproximateSpan
Context triple: [Skyline Arch, hasApproximateSpan, about 21 meters]
  • A. hasApproximateDuration
    Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
  • B. hasApproximateExtent chosen
    Indicates that one entity has a spatial, temporal, or quantitative extent that is only roughly or approximately specified rather than exact.
  • C. hasApproximateEnd
    Indicates that an entity’s end point, time, or boundary is known only approximately rather than precisely.
  • D. hasApproximateValue
    Indicates that one entity’s value is close to, but not exactly equal to, the value of another entity within an acceptable margin of error.
  • E. containsApproximately
    Indicates that one entity holds or includes another entity in a quantity or proportion that is close to, but not exactly, a specified amount.
  • 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_69d6aa979bdc8190bf0e79104cc098c1 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d797e58aec8190bb8ffdc71c0614d2 completed April 9, 2026, 12:13 p.m.
PD Predicate disambiguation batch_69d7440087ac8190aef2e6f6b13b2635 completed April 9, 2026, 6:15 a.m.
Created at: April 8, 2026, 9:25 p.m.