Triple
T11089671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landscape Arch |
E262216
|
entity |
| Predicate | viewingDistanceRequirement |
P60647
|
FINISHED |
| Object | must be viewed from behind fences |
—
|
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: must be viewed from behind fences | Statement: [Landscape Arch, viewingDistanceRequirement, must be viewed from behind fences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewingDistanceRequirement Context triple: [Landscape Arch, viewingDistanceRequirement, must be viewed from behind fences]
-
A.
intendedViewingDistance
chosen
Indicates the distance at which something is meant or designed to be viewed or observed.
-
B.
viewingIs
Indicates that one entity is engaged in the act or state of viewing, observing, or watching another entity.
-
C.
viewingDistanceFromFalls
Indicates the distance from which an observer views or experiences the falls.
-
D.
hasViewingConditions
Indicates that one entity is associated with specific viewing conditions under which it is meant to be observed or evaluated.
-
E.
minimumWorkingDistance
Indicates the shortest allowable distance that must be maintained between two entities for them to operate or interact safely or effectively.
- 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.