Triple
T13338500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Outrage |
E317759
|
entity |
| Predicate | hasNarrativeFocusOn |
P31
|
FINISHED |
| Object | investigation of a crime |
—
|
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: investigation of a crime | Statement: [The Outrage, hasNarrativeFocusOn, investigation of a crime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNarrativeFocusOn Context triple: [The Outrage, hasNarrativeFocusOn, investigation of a crime]
-
A.
hasNarrativeRole
Indicates that an entity participates in a narrative with a specific functional role (e.g., protagonist, antagonist, narrator) relative to the story.
-
B.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
C.
narrativeFocusOfWork
Indicates that a particular element (such as a character, event, or theme) is the primary narrative focus or central subject of a given work.
-
D.
hasNarrative
Indicates that one entity contains, presents, or is associated with a story or narrative about another entity or subject.
-
E.
narrativeSubject
Indicates that an entity functions as the main subject or focal point within a narrative or story.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99d01bf8481908cd3a99e5557b972 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6e53d88190bd6aa42f69b10ffb |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:31 p.m.