Triple
T273911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2028 Summer Olympics |
E5204
|
entity |
| Predicate | expectedToInclude |
P1393
|
FINISHED |
| Object | traditional core Olympic sports |
—
|
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: traditional core Olympic sports | Statement: [2028 Summer Olympics, expectedToInclude, traditional core Olympic sports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expectedToInclude Context triple: [2028 Summer Olympics, expectedToInclude, traditional core Olympic sports]
-
A.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
B.
providedFor
Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
-
C.
meetsAtLeast
Indicates that one entity encounters or comes into contact with another entity at least a specified minimum number of times or to a minimum required degree.
-
D.
endsOn
Indicates that one entity terminates or concludes precisely at the boundary or endpoint of another entity.
-
E.
extendsTo
Indicates that one entity reaches, stretches, or continues its scope, influence, or coverage up to or into another entity.
- 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25dd0a99c819089968a5400c58c5f |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b7345c4819086c21710864a1b42 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.