Triple
T9926805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2032 Summer Paralympics |
E187942
|
entity |
| Predicate | hasPlannedTimeOfYear |
P26282
|
FINISHED |
| Object | austral winter |
—
|
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: austral winter | Statement: [2032 Summer Paralympics, hasPlannedTimeOfYear, austral winter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedTimeOfYear Context triple: [2032 Summer Paralympics, hasPlannedTimeOfYear, austral winter]
-
A.
scheduledInYear
Indicates that an event, activity, or item is planned or set to occur within a specific calendar year.
-
B.
plannedAt
chosen
Indicates that an event, action, or activity is scheduled or intended to occur at a specific time or date.
-
C.
planningYear
Indicates the year in which planning or preparation activities for something are scheduled or designated to occur.
-
D.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
-
E.
hasPlanningStatus
Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
- 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_69ca82b22a688190b52c75bd48429c10 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb59b85f88190899ea279fc02660f |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:43 p.m.