Triple
T2200908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperator Furiosa |
E50484
|
entity |
| Predicate | commandRank |
P342
|
FINISHED |
| Object | high-ranking lieutenant under Immortan Joe |
—
|
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: high-ranking lieutenant under Immortan Joe | Statement: [Imperator Furiosa, commandRank, high-ranking lieutenant under Immortan Joe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandRank Context triple: [Imperator Furiosa, commandRank, high-ranking lieutenant under Immortan Joe]
-
A.
militaryRank
chosen
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
B.
militaryRankOfPrecedence
Indicates the relative seniority or priority order of a military rank compared to other ranks.
-
C.
hasCommanderRank
Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy or context.
-
D.
commandLevel
Indicates the hierarchical degree of authority or control one entity holds over another within a command structure.
-
E.
rankGrade
Indicates the grade or level assigned to an entity within a ranking or evaluation system.
- 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfa06bb4819092d7021358846e5f |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda706f4819094de73e1d1d1f539 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.