Triple
T5351075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunder Run |
E124178
|
entity |
| Predicate | indoorSection |
P61429
|
FINISHED |
| Object | majority of course inside mountain |
—
|
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: majority of course inside mountain | Statement: [Thunder Run, indoorSection, majority of course inside mountain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indoorSection Context triple: [Thunder Run, indoorSection, majority of course inside mountain]
-
A.
indoorOrOutdoor
Indicates whether an activity, event, or entity occurs inside a building (indoors) or outside in open air (outdoors).
-
B.
hasIndoorArea
chosen
Indicates that an entity possesses or includes an area or space that is located indoors or within a building.
-
C.
interiorFloor
Indicates that one entity is the interior floor surface or flooring of another enclosing space or structure.
-
D.
interiorStyle
Indicates that one entity has a particular interior design style or aesthetic characterized by the other entity.
-
E.
primaryIndoorArena
Indicates that one entity serves as the main indoor arena or principal covered sports/entertainment venue for another entity.
- 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_69bd464be27081908807b40b75c1bbae |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd861188ac81908ef2b1f25cc6c864 |
completed | March 20, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69bd845c6f108190832a8d14b356368a |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.