Triple
T25872022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Theologian’s Tale |
E651784
|
entity |
| Predicate | isToldByCharacterIn |
P119452
|
FINISHED |
| Object | Tales of a Wayside Inn |
—
|
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: Tales of a Wayside Inn | Statement: [The Theologian’s Tale, isToldByCharacterIn, Tales of a Wayside Inn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isToldByCharacterIn Context triple: [The Theologian’s Tale, isToldByCharacterIn, Tales of a Wayside Inn]
-
A.
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.
-
B.
narratedByCharacters
chosen
Indicates that the events or content of a work are told or recounted by specific characters within that work.
-
C.
spokenToCharacter
Indicates that one character has verbally addressed or communicated directly with another character.
-
D.
characterStatusInStory
Indicates the role or condition a character holds within the context of a specific story or narrative.
-
E.
appearsInShortStoryBy
Indicates that one entity is a character, element, or subject that appears within a short story authored by another entity.
- 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_69e7ab3ad9d88190841ddcb93ab02e96 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f602dd86dc8190b36335017d158398 |
completed | May 2, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69f4939148dc81908706cec7d85291bc |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 8:11 a.m.