Triple
T33198864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Song of the King |
E849844
|
entity |
| Predicate | performerInNarrative |
P141184
|
FINISHED |
| Object | Pharaoh |
—
|
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: Pharaoh | Statement: [Song of the King, performerInNarrative, Pharaoh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerInNarrative Context triple: [Song of the King, performerInNarrative, Pharaoh]
-
A.
singerInNarrative
chosen
Indicates that one entity serves as the singer or vocal performer within the context or storyline of the other entity (the narrative).
-
B.
narratorPlayedBy
Indicates that a given narrator character is portrayed or voiced by a specific performer or actor.
-
C.
narrativeCharacter
Indicates that one entity functions as a character within the narrative or story associated with another entity.
-
D.
inNarrativeRole
Indicates that one entity participates in relation to another by occupying a specific narrative function or role within a story or discourse.
-
E.
narratorRole
Indicates that one entity serves as the narrator of another entity (such as a story, text, or media work), specifying the narrative role or function it performs.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: May 1, 2026, 1:29 a.m.