Triple
T8425633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Showdown |
E198978
|
entity |
| Predicate | structuralRoleInWork |
P5188
|
FINISHED |
| Object | final confrontation sequence |
—
|
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: final confrontation sequence | Statement: [Showdown, structuralRoleInWork, final confrontation sequence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: structuralRoleInWork Context triple: [Showdown, structuralRoleInWork, final confrontation sequence]
-
A.
workStructure
Indicates how work is organized, arranged, or structured within or between entities.
-
B.
settingOfWork
Indicates the place, time, or environment in which a creative work’s narrative or events are situated.
-
C.
positionInWork
chosen
Indicates the specific role, rank, or placement an entity holds within a larger work or structured composition.
-
D.
partOfWorkStructure
Indicates that one work-related component, role, or task is included within or belongs to a larger organizational or work structure.
-
E.
roleInCommandStructure
Indicates that one entity holds a specific position or function within the hierarchical command structure of another entity or organization.
- 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_69ca8313c99081909a5c6d83b91de5b3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb85a2871081908a4093838fc93b5a |
completed | March 31, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69cb70d7ea348190aafbf8ca02b7b7d5 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:07 p.m.