Triple
T20920995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | men's high jump at the 1936 Summer Olympics |
E515205
|
entity |
| Predicate | jumpingAreaType |
P23143
|
FINISHED |
| Object | high jump apron |
—
|
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 jump apron | Statement: [men's high jump at the 1936 Summer Olympics, jumpingAreaType, high jump apron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jumpingAreaType Context triple: [men's high jump at the 1936 Summer Olympics, jumpingAreaType, high jump apron]
-
A.
hasPlayAreaType
Indicates the specific kind or category of play area associated with an entity (e.g., indoor, outdoor, playground type).
-
B.
arenaType
chosen
Indicates the specific kind or category of arena associated with an entity or event.
-
C.
hasAreaType
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
-
D.
spectatorAreaType
Indicates the specific kind or category of area designated for spectators in a venue or event setting.
-
E.
BASEJumpingStatus
Indicates whether an entity is currently engaged in, has completed, or is otherwise associated with BASE jumping activities.
- 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_69e0b4f9d5ec8190bb2bd27350ed341c |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f64e56bc81908aa86f2176fcc0db |
completed | April 21, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:48 p.m.