Triple
T32871873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege Perilous |
E840813
|
entity |
| Predicate | filledInStoryBy |
P1955
|
FINISHED |
| Object | Sir Galahad at Pentecost |
—
|
NE NERFINISHED |
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: Sir Galahad at Pentecost | Statement: [Siege Perilous, filledInStoryBy, Sir Galahad at Pentecost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filledInStoryBy Context triple: [Siege Perilous, filledInStoryBy, Sir Galahad at Pentecost]
-
A.
storyboardedBy
Indicates that a visual narrative work (such as a film, animation, or sequence) has its scenes or shots planned and illustrated by a specific storyboard artist or creator.
-
B.
storyBy
chosen
Indicates that one entity is the creator or author of the story associated with another entity.
-
C.
wroteIn
Indicates that an entity authored or composed something using a particular language, medium, or writing system.
-
D.
hasAllyInStory
Indicates that one entity is portrayed as an ally or supportive partner of another entity within the context of a specific story or narrative.
-
E.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
- 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:17 a.m.