Triple
T29841331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adventuredome |
E757804
|
entity |
| Predicate | indoorAdvantage |
P167655
|
FINISHED |
| Object | year-round operation regardless of weather |
—
|
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: year-round operation regardless of weather | Statement: [Adventuredome, indoorAdvantage, year-round operation regardless of weather]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indoorAdvantage Context triple: [Adventuredome, indoorAdvantage, year-round operation regardless of weather]
-
A.
indoorTitle
Indicates that an entity holds a title, role, or designation specifically applicable within an indoor context or indoor environment.
-
B.
indoorOrOutdoor
Indicates whether an activity, event, or entity occurs inside a building (indoors) or outside in open air (outdoors).
-
C.
indoorComponent
Indicates that one entity functions as an indoor part, element, or feature of another entity.
-
D.
hasIndoorType
Indicates that an entity is associated with a specific type or category of indoor environment or indoor feature.
-
E.
indoorLocationAdvantage
Indicates that one entity has a positional or strategic advantage over another due to being located indoors.
- F. None of above. chosen
Provenance (4 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6760a7ee88190992cdec8aaaf49fa |
completed | May 2, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66bd123108190b451eb6e23842adb |
completed | May 2, 2026, 9:25 p.m. |
Created at: April 29, 2026, 5:39 p.m.