Triple
T9573783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | speed skating at the 2002 Winter Olympics |
E230991
|
entity |
| Predicate | eventsForMen |
P89885
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [speed skating at the 2002 Winter Olympics, eventsForMen, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventsForMen Context triple: [speed skating at the 2002 Winter Olympics, eventsForMen, 5]
-
A.
sponsorsMenSports
Indicates that a subject provides financial or material support specifically for men’s sports programs or teams.
-
B.
mainEvents
Indicates that the referenced entities are the primary or most significant events within a given context, sequence, or narrative.
-
C.
targetOccasion
Indicates the specific event, situation, or occasion toward which an action, plan, or intention is directed.
-
D.
madeForEvent
Indicates that something was created, produced, or designed specifically for use in a particular event.
-
E.
mainEventFor
Indicates that one event is the primary or central event associated with another entity, such as a context, grouping, or larger occurrence.
- 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_69ca848091c48190bc313d6620d09555 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99a94c788190a4bb5d2b676908ac |
completed | April 1, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69ccd59b960c8190966a8870a2426bd5 |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93e90048190a2b0d7c5c195ba98 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:05 p.m.