Triple
T33556305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mission Song |
E859484
|
entity |
| Predicate | protagonistWorksFor |
P180752
|
FINISHED |
| Object | British intelligence services |
—
|
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: British intelligence services | Statement: [The Mission Song, protagonistWorksFor, British intelligence services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistWorksFor Context triple: [The Mission Song, protagonistWorksFor, British intelligence services]
-
A.
protagonistEmployerLocation
Indicates the location where the protagonist’s employer is based or operates.
-
B.
protagonistParentOccupation
Indicates the occupation or job held by the protagonist’s parent in the described context.
-
C.
protagonistBusiness
Indicates that a business is owned, operated, or primarily associated with the story’s protagonist.
-
D.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
E.
protagonistEmployerFamilyName
Indicates the family name (surname) of the employer of the story’s protagonist.
- 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_69f3497b2b68819093207971b5e13dc8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
| PDg | Predicate description generation | batch_69f74c6fa6548190b03935f65429a24e |
completed | May 3, 2026, 1:23 p.m. |
Created at: May 1, 2026, 1:40 a.m.