Triple
T9968952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nux |
E195753
|
entity |
| Predicate | loyaltyChange |
P91356
|
FINISHED |
| Object | from Immortan Joe to Furiosa and Max |
—
|
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: from Immortan Joe to Furiosa and Max | Statement: [Nux, loyaltyChange, from Immortan Joe to Furiosa and Max]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loyaltyChange Context triple: [Nux, loyaltyChange, from Immortan Joe to Furiosa and Max]
-
A.
loyaltyIncentive
Indicates a relationship where benefits or rewards are provided to encourage or recognize continued commitment or repeat engagement.
-
B.
loyaltyDimension
Indicates the degree or aspect of loyalty characterizing the relationship between entities.
-
C.
loyaltySymbolizedBy
Indicates that an instance of loyalty is represented or expressed by a particular symbol or emblem.
-
D.
loyaltyMechanism
Indicates a mechanism or process through which loyalty is established, maintained, or reinforced between entities.
-
E.
loyaltyDomain
Indicates a relationship where loyalty, allegiance, or steadfast support is directed toward or governed by a particular domain, context, or sphere of influence.
- 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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb7b683ac8190ac97bd775a860d29 |
completed | April 2, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:47 p.m.