Triple
T6082179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrew "Pope" Cody |
E135548
|
entity |
| Predicate | inUniverseActivity |
P68539
|
FINISHED |
| Object | armed robbery |
—
|
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: armed robbery | Statement: [Andrew "Pope" Cody, inUniverseActivity, armed robbery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseActivity Context triple: [Andrew "Pope" Cody, inUniverseActivity, armed robbery]
-
A.
inUniverseEvent
Indicates that an event occurs within, and is governed by the context or rules of, a particular fictional or defined universe.
-
B.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
C.
inUniverseFunction
Indicates that one entity serves a specific role, purpose, or function within the context or rules of a particular fictional or defined universe.
-
D.
inUniverseType
Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
-
E.
inUniverseOrganization
Indicates that an organization exists and operates within a specified fictional or narrative universe.
- 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_69c0087ad31c8190ab936e0ff28614b6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05774bc948190a446b27e83f7079b |
completed | March 22, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c049f21fe08190995df3c5c05fb8ea |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8d4a148190bd8f95caae978e1b |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:11 p.m.