Triple
T38099335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strife |
E951332
|
entity |
| Predicate | hasNarrativeRules |
P201027
|
FINISHED |
| Object | distinct narrative rules |
—
|
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: distinct narrative rules | Statement: [Strife, hasNarrativeRules, distinct narrative rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNarrativeRules Context triple: [Strife, hasNarrativeRules, distinct narrative rules]
-
A.
hasNarrative
Indicates that one entity contains, presents, or is associated with a story or narrative about another entity or subject.
-
B.
hasNarrativeContext
Indicates that an entity is associated with, or situated within, a particular narrative or storytelling context that frames its meaning or role.
-
C.
hasNarrativeRole
Indicates that an entity participates in a narrative with a specific functional role (e.g., protagonist, antagonist, narrator) relative to the story.
-
D.
hasNarrativeOutcome
Indicates that an event, action, or narrative element leads to or results in a particular story-related consequence or resolution.
-
E.
hasNarrativeSegments
Indicates that an entity is composed of or associated with multiple distinct narrative segments or sections.
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffc1550cb481908628e446d9b67f7b |
completed | May 9, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69ffc10a74708190ae90e2c378791f70 |
completed | May 9, 2026, 11:19 p.m. |
| PDg | Predicate description generation | batch_69ffc15434c8819093aa3b33813613be |
completed | May 9, 2026, 11:20 p.m. |
Created at: May 3, 2026, 4:21 p.m.