Triple
T11884061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merchant (The Canterbury Tales) |
E282730
|
entity |
| Predicate | taleFocus |
P31266
|
FINISHED |
| Object | marriage |
—
|
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: marriage | Statement: [Merchant (The Canterbury Tales), taleFocus, marriage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taleFocus Context triple: [Merchant (The Canterbury Tales), taleFocus, marriage]
-
A.
narrativeFocusOfWork
chosen
Indicates that a particular element (such as a character, event, or theme) is the primary narrative focus or central subject of a given work.
-
B.
characterizationFocus
Indicates that the primary emphasis or concern of a characterization is directed toward a particular aspect, feature, or dimension of the subject.
-
C.
coreNarrative
Indicates the primary storyline or central sequence of events that forms the main thread of a narrative.
-
D.
narrativeFrame
Indicates the overarching narrative context or perspective within which events, actions, or relationships are presented or interpreted.
-
E.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d3a02ad4819090faef0e0be732ee |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb272f88819090c37c944c5a60ab |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.