Triple
T22171663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lone Wolf |
E547933
|
entity |
| Predicate | primaryRoleInStories |
P42552
|
FINISHED |
| Object | detective |
—
|
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: detective | Statement: [The Lone Wolf, primaryRoleInStories, detective]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRoleInStories Context triple: [The Lone Wolf, primaryRoleInStories, detective]
-
A.
roleInStories
chosen
Indicates the specific function, position, or character part an entity plays within one or more stories.
-
B.
principalRoleIn
Indicates that an entity holds the primary or leading role in a particular context, activity, or relationship.
-
C.
primaryRoleOnLine
Indicates that an entity serves as the main or most important role associated with a particular line (such as a transit line, product line, or communication line).
-
D.
primaryPersona
Indicates that one entity is the main or most representative persona associated with another entity, distinguishing it from any secondary or supporting personas.
-
E.
currentPrimaryRole
Indicates the role an entity is presently holding as its main or most important function or position.
- 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.