Triple
T28389050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One Tree Observation Deck |
E719099
|
entity |
| Predicate | primaryTimeOfVisit |
P31097
|
FINISHED |
| Object | night |
—
|
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: night | Statement: [One Tree Observation Deck, primaryTimeOfVisit, night]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTimeOfVisit Context triple: [One Tree Observation Deck, primaryTimeOfVisit, night]
-
A.
primaryEngagementDate
Indicates the date on which the first or main engagement, commitment, or formal involvement between the related entities was initially established.
-
B.
wasFirstVisitedBy
Indicates that a particular entity was initially reached, discovered, or visited by another specified entity before any others.
-
C.
bestVisitedAt
chosen
Indicates the optimal time or conditions under which a place or entity should be visited.
-
D.
hasVisitingTime
Indicates that there is a specified time period during which visits are allowed or scheduled for an entity.
-
E.
firstPerformedOn
Indicates the date or occasion on which an action, event, or performance was carried out for the first time on a particular subject or object.
- 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_6a002f0839fc8190a874d3b0d0826d7e |
completed | May 10, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_6a002eae7b6481909974b321e2789b7e |
completed | May 10, 2026, 7:07 a.m. |
Created at: April 28, 2026, 1:12 a.m.