Triple
T35709541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poupée de cire, poupée de son |
E1031813
|
entity |
| Predicate | resultInContest |
P8651
|
FINISHED |
| Object | winner |
—
|
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: winner | Statement: [Poupée de cire, poupée de son, resultInContest, winner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultInContest Context triple: [Poupée de cire, poupée de son, resultInContest, winner]
-
A.
competitionResult
chosen
Indicates the outcome of a competitive event, specifying how participants placed or performed relative to one another.
-
B.
resultOfParticipation
Indicates that something occurs or is produced as a consequence of an entity’s participation in an event or activity.
-
C.
resultContested
Indicates that the outcome or result of an event, process, or decision is being challenged or disputed by one or more parties.
-
D.
competitionEnd
Indicates that a competitive event or contest has concluded or reached its final state.
-
E.
submissionDecidesWinner
Indicates that the outcome or winner of a contest, match, or decision process is determined by a submission made by a participant.
- 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_69f76e0df1d08190965b1c6dff94c391 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 3, 2026, 4:05 p.m.