Triple
T15504977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mile High |
E379056
|
entity |
| Predicate | homeFieldAdvantageReason |
P10853
|
FINISHED |
| Object | high altitude |
—
|
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 altitude | Statement: [Mile High, homeFieldAdvantageReason, high altitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeFieldAdvantageReason Context triple: [Mile High, homeFieldAdvantageReason, high altitude]
-
A.
homeFieldAdvantageFor
Indicates that one entity benefits from playing or operating in its own familiar location or environment when facing the other entity.
-
B.
homeFieldAdvantageBasedOn
chosen
Indicates that the degree of home-field advantage is determined or influenced by the specified factor or condition.
-
C.
homeFieldAdvantage
Indicates that one participant benefits from playing or operating in a familiar or home environment, gaining an advantage over the opponent.
-
D.
homeFieldLocation
Indicates the location where an entity’s primary or home field, venue, or playing ground is situated.
-
E.
homeCourtAdvantageFor
Indicates that one party benefits from playing or competing on its own familiar venue or territory against another party.
- 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03fcd5d948190b25a67a72ef980e9 |
completed | April 16, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:55 a.m.