Triple
T26544029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock the Cradle |
E671471
|
entity |
| Predicate | hasCompetitionOutcome |
P33358
|
FINISHED |
| Object | winner selected |
—
|
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 selected | Statement: [Rock the Cradle, hasCompetitionOutcome, winner selected]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompetitionOutcome Context triple: [Rock the Cradle, hasCompetitionOutcome, winner selected]
-
A.
hasWonCompetition
Indicates that an entity has achieved victory in a competition or contest against others.
-
B.
hasEventOutcome
chosen
Indicates that a particular event results in, leads to, or is associated with a specific outcome.
-
C.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
-
D.
competitionResult
Indicates the outcome of a competitive event, specifying how participants placed or performed relative to one another.
-
E.
championshipOutcome
Indicates the result or final standing of a competitor or team in a championship event.
- 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_69eeb3206e748190b90c85cc81f38c91 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
Created at: April 27, 2026, 1:43 a.m.