Triple
T14059280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Arch |
E338301
|
entity |
| Predicate | viewDependentOn |
P41478
|
FINISHED |
| Object | changing light conditions |
—
|
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: changing light conditions | Statement: [The Arch, viewDependentOn, changing light conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewDependentOn Context triple: [The Arch, viewDependentOn, changing light conditions]
-
A.
observerDependent
chosen
Indicates that the truth, value, or manifestation of something varies depending on which observer is considering or measuring it.
-
B.
representationDependsOn
Indicates that one representation is reliant on or derived from another representation in order to be valid, complete, or interpretable.
-
C.
viewIs
Indicates that one entity is a visual representation or perspective of another entity.
-
D.
positionDependsOn
Indicates that the spatial or ordered position of one entity is determined or constrained by the position of another entity.
-
E.
viewOnValue
Indicates a relationship where one entity holds or expresses a particular perspective, opinion, or stance regarding a specific value or principle.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5686f51c81908c33143ecbaae83d |
completed | April 14, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.