Triple
T31916100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairytale |
E814835
|
entity |
| Predicate | contestResult |
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: [Fairytale, contestResult, winner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contestResult Context triple: [Fairytale, contestResult, winner]
-
A.
competitionResult
chosen
Indicates the outcome of a competitive event, specifying how participants placed or performed relative to one another.
-
B.
competitionEnd
Indicates that a competitive event or contest has concluded or reached its final state.
-
C.
eventResult
Indicates that one event occurs as a consequence or outcome of another event.
-
D.
sportsOutcome
Indicates the result or final status of a sporting event or competition between participants.
-
E.
resultOfParticipation
Indicates that something occurs or is produced as a consequence of an entity’s participation in an event or activity.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: May 1, 2026, 12:02 a.m.