Triple
T27872075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resistance |
E704815
|
entity |
| Predicate | hasEnemyLeader |
P174359
|
FINISHED |
| Object | Supreme Leader Snoke |
—
|
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: Supreme Leader Snoke | Statement: [Resistance, hasEnemyLeader, Supreme Leader Snoke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnemyLeader Context triple: [Resistance, hasEnemyLeader, Supreme Leader Snoke]
-
A.
hasAlliedLeader
Indicates that one entity serves as an allied leader or commander in relation to another entity.
-
B.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
C.
hasCommander
Indicates that one entity serves as the commanding officer or leader of another entity.
-
D.
hasConqueringKing
Indicates that an entity has a king who has conquered or taken control over it or its territory.
-
E.
belligerentLeader
Indicates that an entity serves as a leader or authority figure of a party engaged in a conflict, war, or hostile confrontation.
- F. None of above. chosen
Provenance (4 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6c20f209081909fb9ac8f95069f04 |
completed | May 3, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c125695c81909704c67bef4ce5b2 |
completed | May 3, 2026, 3:29 a.m. |
Created at: April 27, 2026, 6:25 p.m.