Triple
T28759119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | football at the 1928 Summer Olympics |
E731757
|
entity |
| Predicate | includedBronzeMedalMatch |
P10836
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [football at the 1928 Summer Olympics, includedBronzeMedalMatch, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedBronzeMedalMatch Context triple: [football at the 1928 Summer Olympics, includedBronzeMedalMatch, true]
-
A.
bronzeMedalGameMatchup
Indicates the matchup between competitors or teams that determines the winner of the bronze medal in a competition or tournament.
-
B.
olympicBronzeMedalBronzeMatchScore
Indicates the score achieved in the bronze-medal (third-place) match that determined the awarding of an Olympic bronze medal.
-
C.
includesMedal
chosen
Indicates that an entity’s set, collection, or record contains or features a particular medal as one of its elements.
-
D.
olympicBronzeMedalOpponentInBronzeMatch
Indicates that one entity was the opponent of the other in the bronze medal match at the Olympic Games.
-
E.
bronzeMedalist
Indicates that an entity finished third in a competition or event, earning the bronze medal.
- 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69ff2d22ffb48190ae58ddf3c7e02869 |
completed | May 9, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69ff2ac2e1c4819096cc64e94aef2ff0 |
completed | May 9, 2026, 12:38 p.m. |
Created at: April 28, 2026, 6:11 a.m.