Triple
T32150343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commère |
E821142
|
entity |
| Predicate | partOfNarrativeStyle |
P26602
|
FINISHED |
| Object | experimental narrative |
—
|
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: experimental narrative | Statement: [Commère, partOfNarrativeStyle, experimental narrative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfNarrativeStyle Context triple: [Commère, partOfNarrativeStyle, experimental narrative]
-
A.
narrativeStyle
Indicates how a narrative is told, such as the point of view, tone, and structural approach used to present a story or account.
-
B.
appearsInNarrativeStyle
Indicates that one entity is presented or expressed using the narrative style, voice, or storytelling mode associated with another entity.
-
C.
usesNarrativeStyle
chosen
Indicates that one entity employs or adopts a particular narrative style in presenting or structuring content or information.
-
D.
narrativeStrategy
Indicates the method or approach used to structure, present, or convey a story or sequence of events.
-
E.
hasPartInNarrative
Indicates that one entity plays a role or participates as a component within the storyline or structure of another narrative 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff891e4b9c8190aa86a339a8944496 |
completed | May 9, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69ff8801180c8190b23e20996ca68e0a |
completed | May 9, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:31 a.m.