Triple
T32558676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | War Boys |
E832160
|
entity |
| Predicate | followsLeader |
P34528
|
FINISHED |
| Object | Immortan Joe |
—
|
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: Immortan Joe | Statement: [War Boys, followsLeader, Immortan Joe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsLeader Context triple: [War Boys, followsLeader, Immortan Joe]
-
A.
followsLeadershipOf
chosen
Indicates that one entity accepts and acts under the guidance, direction, or authority of another entity’s leadership.
-
B.
linkedToLeader
Indicates that an entity has a direct connection, association, or relationship with a leader.
-
C.
laterLeader
Indicates that one entity serves as a leader or holds a leadership role at a later time than another specified leader.
-
D.
establishedUnderLeader
Indicates that an entity was founded, created, or formally established during the tenure or authority of a specific leader.
-
E.
targetLeader
Indicates that one entity is the primary leader, focal authority, or main decision-maker targeted or referenced by another entity or action.
- 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: May 1, 2026, 1:03 a.m.