Triple
T24431994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reaper War |
E616021
|
entity |
| Predicate | primaryProtagonistSide |
P47185
|
FINISHED |
| Object | Systems Alliance |
—
|
NE NERFINISHED |
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: Systems Alliance | Statement: [Reaper War, primaryProtagonistSide, Systems Alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryProtagonistSide Context triple: [Reaper War, primaryProtagonistSide, Systems Alliance]
-
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.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
D.
primaryAlly
Indicates that one entity is the main or most significant ally or supportive partner of another entity.
-
E.
secondaryProtagonistType
Indicates the role or category of a work’s secondary main character in relation to the primary protagonist.
- 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_69e2d7ec44b081909ccaf1f3bbec0641 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29783b3208190997c47be1aa229af |
completed | April 29, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:16 a.m.