Triple
T25752396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Brothers |
E648500
|
entity |
| Predicate | exploresRoleOf |
P117092
|
FINISHED |
| Object | Director of Central Intelligence |
E33204
|
NE 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: Director of Central Intelligence | Statement: [The Brothers, exploresRoleOf, Director of Central Intelligence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploresRoleOf Context triple: [The Brothers, exploresRoleOf, Director of Central Intelligence]
-
A.
strategicRoleIn
Indicates that one entity serves a strategic function, position, or importance within the context, operations, or objectives of another entity.
-
B.
loreRole
Indicates the specific narrative or canonical function an entity fulfills within a fictional or mythological lore.
-
C.
expandsRoleOf
Indicates that one entity broadens, extends, or adds responsibilities to the role or function defined by another entity.
-
D.
highlightsRole
chosen
Indicates that one entity emphasizes, showcases, or draws special attention to the role or function of another entity.
-
E.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
- F. None of above.
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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f600c18a14819081b5914dd3b0f9cf |
completed | May 2, 2026, 1:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a10cc1095f081908a9c722e059d834a |
completed | May 22, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 22, 2026, 4:36 a.m.