Triple
T16525296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Enemy |
E401418
|
entity |
| Predicate | narrativeRoleForJackReacher |
P83930
|
FINISHED |
| Object | prequel |
—
|
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: prequel | Statement: [The Enemy, narrativeRoleForJackReacher, prequel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeRoleForJackReacher Context triple: [The Enemy, narrativeRoleForJackReacher, prequel]
-
A.
inNarrativeRole
Indicates that one entity participates in relation to another by occupying a specific narrative function or role within a story or discourse.
-
B.
narratorRole
Indicates that one entity serves as the narrator of another entity (such as a story, text, or media work), specifying the narrative role or function it performs.
-
C.
metaNarrativeRole
Indicates the narrative function or role that one element (such as a character, voice, or device) plays in commenting on, framing, or reflecting the story itself at a meta-level.
-
D.
narrativeRoleInSeries
chosen
Indicates the specific narrative function or role an entity plays within a particular series or serialized work.
-
E.
narrativeCharacter
Indicates that one entity functions as a character within the narrative or story associated with another entity.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32ed323c081908218460aa4ae3cf6 |
completed | April 18, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.