Triple
T33406577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Five Wives of Immortan Joe |
E855452
|
entity |
| Predicate | residesAtStartOfStory |
P37669
|
FINISHED |
| Object | Citadel harem |
—
|
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: Citadel harem | Statement: [The Five Wives of Immortan Joe, residesAtStartOfStory, Citadel harem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residesAtStartOfStory Context triple: [The Five Wives of Immortan Joe, residesAtStartOfStory, Citadel harem]
-
A.
firstRegularStory
Indicates that an entity is the earliest or primary standard (non-special) story associated with another entity in a sequence or collection.
-
B.
positionInStory
chosen
Indicates the point or role an event, character, or element occupies within the overall sequence or structure of a story.
-
C.
residenceAtStartOfFilm
Indicates the place where a person or character is living at the beginning of the film.
-
D.
protagonistStatusAtStart
Indicates the role or condition the main character is in at the beginning of the narrative or event.
-
E.
narrativeStart
Indicates the point or event at which a narrative, story, or sequence of events begins.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e47f37848190aadb137c81760f1f |
completed | May 3, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:36 a.m.