Triple
T7968780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2028 Summer Paralympics |
E185272
|
entity |
| Predicate | scheduledIn |
P42174
|
FINISHED |
| Object | 2028 |
—
|
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: 2028 | Statement: [2028 Summer Paralympics, scheduledIn, 2028]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scheduledIn Context triple: [2028 Summer Paralympics, scheduledIn, 2028]
-
A.
scheduledAs
Indicates that one entity is assigned or arranged to occur or function in the role, time, or capacity specified by another entity within a schedule.
-
B.
scheduledDuring
Indicates that one event or activity is planned to occur within the time interval defined by another event or period.
-
C.
scheduledInYear
chosen
Indicates that an event, activity, or item is planned or set to occur within a specific calendar year.
-
D.
scheduleUS
Indicates that an entity arranges or assigns a time for something specifically within the context of the United States.
-
E.
schedule
Indicates that an entity arranges for an event, task, or activity to occur at a specific time or within a defined time frame.
- 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_69ca8297699481909b75a405f01e03af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3bd06ee081908c5080003fb7b8f7 |
completed | March 31, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69cb047a8e4c81909b79e0f0bf56440c |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:13 p.m.