Triple
T2070132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soldier Hollow |
E44796
|
entity |
| Predicate | postOlympicUse |
P32076
|
FINISHED |
| Object | public recreational skiing |
—
|
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: public recreational skiing | Statement: [Soldier Hollow, postOlympicUse, public recreational skiing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postOlympicUse Context triple: [Soldier Hollow, postOlympicUse, public recreational skiing]
-
A.
primaryUseAfterOlympics
chosen
Indicates the main function or purpose a venue or facility is intended to serve after the Olympic Games have concluded.
-
B.
postOlympicsCapacity
Indicates the seating or usage capacity of a venue after the Olympic Games have concluded.
-
C.
olympicGames
Indicates that an entity is an edition or instance of the Olympic Games event.
-
D.
olympicCommittee
Indicates that an entity serves as, belongs to, or is officially associated with an Olympic committee in relation to another entity.
-
E.
hasOlympicFunction
Indicates that an entity serves a specific role, duty, or function within the context of the Olympic Games or Olympic movement.
- 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_69a88916c2b48190a5ca2e9b12cad3ed |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9f677108190aea3c8db7850c892 |
completed | March 7, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69abb7aee9b48190999620176e3a6ee2 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:41 p.m.