Triple
T28759120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | football at the 1928 Summer Olympics |
E731757
|
entity |
| Predicate | includedReplayMatches |
P199311
|
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, includedReplayMatches, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedReplayMatches Context triple: [football at the 1928 Summer Olympics, includedReplayMatches, true]
-
A.
matchesPlayedIn
Indicates that a particular match was played in a specified location, event, or competition context.
-
B.
playedInMatch
Indicates that an entity participated as a player in a particular match.
-
C.
includesRecordingsBy
Indicates that one entity (such as a collection, album, or compilation) contains or features recordings created or performed by another entity (such as an artist or group).
-
D.
isReplay
Indicates that an event, action, or content instance is a repeated playback or reproduction of a previously occurring original.
-
E.
hasReplay
Indicates that an event, action, or interaction is available to be viewed or experienced again in a recorded or reconstructed form.
- 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
| PDg | Predicate description generation | batch_69ff2eb0c0888190b0e05a03bf06d388 |
completed | May 9, 2026, 12:55 p.m. |
Created at: April 28, 2026, 6:11 a.m.