Triple
T16485260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bergisel Stadium |
E400421
|
entity |
| Predicate | hasInrunLength |
P122966
|
FINISHED |
| Object | approx. 98 m |
—
|
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: approx. 98 m | Statement: [Bergisel Stadium, hasInrunLength, approx. 98 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInrunLength Context triple: [Bergisel Stadium, hasInrunLength, approx. 98 m]
-
A.
hasShortRun
Indicates that an entity has a brief or limited-duration run or operational period.
-
B.
hasLongChartRunIn
Indicates that something (typically a song, album, or similar work) remained on a specified chart for an extended, continuous period of time.
-
C.
hasCycleLength
Indicates that an entity participates in or exhibits a cycle whose duration or size is specified by the associated length value.
-
D.
hasRunType
Indicates the type or category of a run associated with an entity (e.g., execution mode, run classification, or run configuration).
-
E.
hasTrailLength
Indicates that an entity (such as a trail or route) has a specific measured length.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e05bf448190947b9da15fd29d0a |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:13 a.m.