Triple
T29637666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Licence Renewed |
E755763
|
entity |
| Predicate | protagonistCodeNumber |
P138880
|
FINISHED |
| Object | 007 |
—
|
NE NERFINISHED |
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: 007 | Statement: [Licence Renewed, protagonistCodeNumber, 007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistCodeNumber Context triple: [Licence Renewed, protagonistCodeNumber, 007]
-
A.
mainCharacterCodeNumber
chosen
Indicates that an entity is identified as the primary or central character by a specific code number.
-
B.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
C.
protagonistDefaultName
Indicates that an entity is the default or canonical name assigned to the protagonist in a given work or context.
-
D.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
E.
protagonistType
Indicates the role or category that the main character (protagonist) of a story or scenario belongs to.
- 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_69f0ef88fbe081908f0ad90c1c413f1c |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 28, 2026, 6:45 p.m.