Triple
T30950597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephan Moccio |
E788528
|
entity |
| Predicate | coWroteForEvent |
P47055
|
FINISHED |
| Object | 2010 Winter Olympics |
—
|
NE NERFINISHED |
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: 2010 Winter Olympics | Statement: [Stephan Moccio, coWroteForEvent, 2010 Winter Olympics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coWroteForEvent Context triple: [Stephan Moccio, coWroteForEvent, 2010 Winter Olympics]
-
A.
writtenForEvent
Indicates that something (typically a work or piece) was created specifically for a particular event or occasion.
-
B.
writesAboutEvent
Indicates that an entity creates written content whose subject is a particular event.
-
C.
workWrittenFor
Indicates that a creative work was specifically composed, produced, or created for a particular person, group, event, purpose, or medium.
-
D.
hasWritingCreditOn
chosen
Indicates that an entity is credited as a writer or co-writer for a particular work or production.
-
E.
hasWrittenFor
Indicates that one entity has created written content (such as articles, stories, or texts) for or on behalf of another entity, typically a publication, organization, or platform.
- 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:53 p.m.