Triple
T29947334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seema Raja |
E760669
|
entity |
| Predicate | hasHeroCentricNarrative |
P133183
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Seema Raja, hasHeroCentricNarrative, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeroCentricNarrative Context triple: [Seema Raja, hasHeroCentricNarrative, true]
-
A.
hasNarrative
Indicates that one entity contains, presents, or is associated with a story or narrative about another entity or subject.
-
B.
hasNarrativeRole
Indicates that an entity participates in a narrative with a specific functional role (e.g., protagonist, antagonist, narrator) relative to the story.
-
C.
isNarrativeDriven
Indicates that an entity’s primary structure or progression is guided by a storyline or plot rather than by mechanics, data, or other non-story elements.
-
D.
narrativelyCenteredIn
chosen
Indicates that an event, character, or element is positioned as the primary focus or organizing center of a narrative within a given context.
-
E.
hasTenseNarrative
Indicates that a narrative is expressed using a specific grammatical tense or set of tenses.
- 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 29, 2026, 6:24 p.m.