Triple
T25166621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WCW World Television Championship |
E630196
|
entity |
| Predicate | scriptOutcome |
P108533
|
FINISHED |
| Object | predetermined by bookers |
—
|
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: predetermined by bookers | Statement: [WCW World Television Championship, scriptOutcome, predetermined by bookers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptOutcome Context triple: [WCW World Television Championship, scriptOutcome, predetermined by bookers]
-
A.
scriptedOutcome
chosen
Indicates that the outcome of an event or interaction is predetermined or controlled according to a script rather than arising spontaneously.
-
B.
script
Indicates that an entity is associated with a written text or code (such as a screenplay, program, or written instructions) that defines its content or behavior.
-
C.
scriptEvolution
Indicates how a script or written system changes, develops, or transforms over time in relation to its earlier or later forms.
-
D.
planOutcome
Indicates the result or consequence that is expected or produced by a given plan.
-
E.
serviceOutcome
Indicates the result, consequence, or effect produced by performing a particular service.
- 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_69e75a87c9b88190ab60731902a99750 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46d42ec0081908231beebf495cf3e |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 12:17 p.m.