Triple
T22171664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lone Wolf |
E547933
|
entity |
| Predicate | secondaryRoleInStories |
P42552
|
FINISHED |
| Object | thief |
—
|
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: thief | Statement: [The Lone Wolf, secondaryRoleInStories, thief]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryRoleInStories Context triple: [The Lone Wolf, secondaryRoleInStories, thief]
-
A.
secondaryProtagonistType
Indicates the role or category of a work’s secondary main character in relation to the primary protagonist.
-
B.
roleInStories
chosen
Indicates the specific function, position, or character part an entity plays within one or more stories.
-
C.
laterPrimaryRole
Indicates that an entity assumes a specified primary role at a later time than another role or state in a sequence.
-
D.
secondaryProtagonistCelebrated
Indicates that a secondary protagonist is being honored, praised, or widely recognized for their actions or role.
-
E.
secondHouseRole
Indicates that an entity serves as the second most prominent or secondary role within a particular house or household.
- 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_69e11e3d53f88190a2b690e3f25bb062 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a68c26c8190b1258595bd96cb63 |
completed | April 28, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:34 p.m.