Triple
T12653117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Club Bolívar |
E302213
|
entity |
| Predicate | hasHomeGroundAltitude |
P26519
|
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: [Club Bolívar, hasHomeGroundAltitude, high altitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeGroundAltitude Context triple: [Club Bolívar, hasHomeGroundAltitude, high altitude]
-
A.
hasAltitudeFeature
Indicates that an entity possesses a characteristic or attribute related to its elevation or vertical position above a reference level.
-
B.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
C.
elevationOfHomeField
chosen
Indicates the height above sea level at which a team's home field is located.
-
D.
hasAltitudeStation
Indicates that something is associated with or located at a station characterized by a specific altitude.
-
E.
hasApproxElevationFeet
Indicates that an entity is associated with an elevation value measured in feet that is approximate rather than exact.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b78ce8819091f15dd5013e6da5 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:18 p.m.