Triple
T23444397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Caine as John Tarrant |
E565493
|
entity |
| Predicate | spyFictionSubgenre |
P152313
|
FINISHED |
| Object | ColdWarEraSpyThriller |
—
|
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: ColdWarEraSpyThriller | Statement: [Michael Caine as John Tarrant, spyFictionSubgenre, ColdWarEraSpyThriller]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spyFictionSubgenre Context triple: [Michael Caine as John Tarrant, spyFictionSubgenre, ColdWarEraSpyThriller]
-
A.
hasFictionalSpy
Indicates that an entity includes, features, or is associated with a fictional spy character.
-
B.
involvesEspionage
Indicates that the relationship or action includes spying, covert information gathering, or other secret intelligence activities.
-
C.
fictionalDetective
Indicates that the subject is a detective character who exists only in fiction rather than in real life.
-
D.
secretAction
Indicates that an action is performed in a concealed or confidential manner, hidden from some or all other parties.
-
E.
secretProject
Indicates that an entity is involved in, associated with, or designated as a confidential or undisclosed project.
- F. None of above. chosen
Provenance (4 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_69e24584f9488190bb32730bd2ce023e |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a64717d08190a2c25e7bbfc17a2f |
completed | April 29, 2026, 6:33 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:51 p.m.