Triple
T27810684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Era of the First Order–Resistance conflict |
E702509
|
entity |
| Predicate | hasPrimaryProtagonistFaction |
P47185
|
FINISHED |
| Object | Resistance |
—
|
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: Resistance | Statement: [Era of the First Order–Resistance conflict, hasPrimaryProtagonistFaction, Resistance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryProtagonistFaction Context triple: [Era of the First Order–Resistance conflict, hasPrimaryProtagonistFaction, Resistance]
-
A.
protagonistAllegiance
chosen
Indicates the group, cause, or side with which the main character is aligned or to which they show loyalty.
-
B.
hasProtagonistGroup
Indicates that a narrative work features a central group of characters who collectively serve as the main protagonists.
-
C.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
D.
hasChildProtagonist
Indicates that the work features a child as its main or central character.
-
E.
hasHeroFaction
Indicates that an entity is associated with or belongs to a particular hero-aligned faction.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: April 27, 2026, 5:42 p.m.