Triple
T16164495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Brown |
E392265
|
entity |
| Predicate | fictionalRoleRank |
P110719
|
FINISHED |
| Object | head of MI6 |
—
|
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: head of MI6 | Statement: [Robert Brown, fictionalRoleRank, head of MI6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalRoleRank Context triple: [Robert Brown, fictionalRoleRank, head of MI6]
-
A.
protagonistRank
Indicates the relative narrative importance or centrality of a character within a story, typically ranking how primary they are as a protagonist compared to others.
-
B.
rankingRole
chosen
Indicates that one entity holds a specific position or level in an ordered hierarchy or ranking relative to others.
-
C.
fictionalUniverseRole
Indicates the role or function an entity has within a particular fictional universe or narrative setting.
-
D.
hasFictionalRole
Indicates that an entity plays or is assigned a specific role within a fictional work or narrative.
-
E.
creativeRole
Indicates that an entity holds a specific creative function or responsibility in relation to another entity, such as a work or project.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21e622ae481909f3cf25b38886d3a |
completed | April 17, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69e1828abb608190a99d86bce1d77de2 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:02 a.m.