Triple
T25201391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhys |
E631133
|
entity |
| Predicate | narratesWith |
P159728
|
FINISHED |
| Object | Fiona |
—
|
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: Fiona | Statement: [Rhys, narratesWith, Fiona]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narratesWith Context triple: [Rhys, narratesWith, Fiona]
-
A.
narratesAs
Indicates that one entity tells, recounts, or presents a story, event, or information in the manner, style, or voice of another entity.
-
B.
narratedTo
Indicates that one entity tells or recounts a story, event, or information directly to another entity as the audience.
-
C.
containsNarrativeOf
Indicates that one entity includes or presents the story, account, or narrative content of another entity.
-
D.
narratorOf
Indicates that one entity serves as the narrator or storytelling voice for another entity, such as a text, story, or media work.
-
E.
narratorIn
Indicates that one entity serves as the narrator or storytelling voice within the context of another entity (such as a work, scene, or narrative segment).
- F. None of above. chosen
Provenance (4 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f5f7a205688190b8f36bff5013247c |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 21, 2026, 12:51 p.m.