Triple
T16525105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tripwire |
E401413
|
entity |
| Predicate | literaryCharacterRole |
P15535
|
FINISHED |
| Object | Jack Reacher as protagonist |
—
|
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: Jack Reacher as protagonist | Statement: [Tripwire, literaryCharacterRole, Jack Reacher as protagonist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literaryCharacterRole Context triple: [Tripwire, literaryCharacterRole, Jack Reacher as protagonist]
-
A.
literaryRole
chosen
Indicates the specific narrative or functional role an entity holds within a literary work or text.
-
B.
featuresCharacterRole
Indicates that a work includes a character appearing in a specific narrative or functional role.
-
C.
narrativeCharacter
Indicates that one entity functions as a character within the narrative or story associated with another entity.
-
D.
storyCharacterizedAs
Indicates that a story is described, portrayed, or defined as having a particular quality, style, or attribute.
-
E.
dramaticStructureRole
Indicates the specific function or role an element plays within the overall dramatic structure of a narrative or performance.
- 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.