Triple
T38108544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Friar's Tale |
E951587
|
entity |
| Predicate | taleToldBy |
P102058
|
FINISHED |
| Object | the Friar |
—
|
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: the Friar | Statement: [The Friar's Tale, taleToldBy, the Friar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taleToldBy Context triple: [The Friar's Tale, taleToldBy, the Friar]
-
A.
storyToldFrom
Indicates that a story is narrated or presented from the perspective or viewpoint of a particular entity.
-
B.
storyTime
Indicates that one entity is narrating or sharing a story with another entity, typically in a designated or scheduled period for storytelling.
-
C.
tellsStoriesIn
Indicates that one entity narrates or recounts stories within or to the context of another entity (such as a place, group, or medium).
-
D.
associatedTale
chosen
Indicates that one entity is linked or connected to a particular tale, story, or narrative.
-
E.
storyBy
Indicates that one entity is the creator or author of the story associated with 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_69f76f065ed08190bdfb1b6d817f5b39 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:21 p.m.