Triple
T9133775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doomwar |
E219150
|
entity |
| Predicate | protagonistSide |
P47185
|
FINISHED |
| Object | Black Panther and his allies |
—
|
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: Black Panther and his allies | Statement: [Doomwar, protagonistSide, Black Panther and his allies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistSide Context triple: [Doomwar, protagonistSide, Black Panther and his allies]
-
A.
protagonistAllegiance
chosen
Indicates the group, cause, or side with which the main character is aligned or to which they show loyalty.
-
B.
coProtagonist
Indicates that two or more entities share the primary leading role together in the same narrative work.
-
C.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
D.
conflictSide
Indicates that an entity participates as a distinct party or faction on one side of a conflict or dispute.
-
E.
protagonistField
Indicates that the subject is the main or central character (protagonist) within the specified narrative or context.
- 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_69ca83debfc0819095800583e97ab10f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8dccecc81908d8fc641c419ca6a |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc6601d77881908299d58db6e64937 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:18 p.m.