Triple
T20920979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | men's high jump at the 1936 Summer Olympics |
E515205
|
entity |
| Predicate | qualificationHeight |
P141683
|
FINISHED |
| Object | 1.90 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: 1.90 m | Statement: [men's high jump at the 1936 Summer Olympics, qualificationHeight, 1.90 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualificationHeight Context triple: [men's high jump at the 1936 Summer Olympics, qualificationHeight, 1.90 m]
-
A.
qualificationLevel
Indicates the degree or rank of competence, certification, or formal credentials required for or possessed in relation to something.
-
B.
hasQualification
Indicates that an entity possesses a specific qualification, credential, or competency.
-
C.
eligibilityLevel
Indicates the degree or tier of qualification an entity has for a given benefit, service, or status.
-
D.
eligibleRank
Indicates that an entity meets the required rank or level criteria to qualify for a specific role, action, or benefit.
-
E.
qualifyingFor
Indicates that one entity meets the necessary conditions or criteria to be eligible for another entity, status, or action.
- 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_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. |
| PDg | Predicate description generation | batch_69e5d53d22d08190bc17ed4bed53804a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:48 p.m.