Triple
T15328116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Rocks |
E366463
|
entity |
| Predicate | homeMeetAtmosphere |
P118137
|
FINISHED |
| Object | high-attendance |
—
|
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: high-attendance | Statement: [Red Rocks, homeMeetAtmosphere, high-attendance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeMeetAtmosphere Context triple: [Red Rocks, homeMeetAtmosphere, high-attendance]
-
A.
hasAtmosphere
Indicates that an astronomical body possesses a surrounding layer of gases held by its gravity.
-
B.
hasAtmosphericArrangement
Indicates that one entity possesses or exhibits a particular configuration or structure of atmospheric components or layers in relation to another entity or defined standard.
-
C.
homeAtmosphereReputation
Indicates the perceived quality or character of the atmosphere or environment associated with a particular home.
-
D.
atmosphereStatus
Indicates the current condition or state of an atmosphere, such as its composition, quality, or environmental status.
-
E.
homeMeetsVenue
Indicates that a home team plays its scheduled match at a specified venue.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dffd6f88190a0f031ee90c6a7d2 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2e413481909d9180a8d78d2c17 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:16 a.m.