Triple
T14357900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honoré d’Urfé |
E356017
|
entity |
| Predicate | literaryFormOfL'Astrée |
P6480
|
FINISHED |
| Object | prose romance |
—
|
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: prose romance | Statement: [Honoré d’Urfé, literaryFormOfL'Astrée, prose romance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literaryFormOfL'Astrée Context triple: [Honoré d’Urfé, literaryFormOfL'Astrée, prose romance]
-
A.
hasLiteraryForm
chosen
Indicates that one entity is expressed, structured, or realized in a particular literary form (such as a genre, style, or textual format).
-
B.
literaryUnit
Indicates that one entity is a distinct segment or component (such as a chapter, scene, or passage) within a larger literary work or text.
-
C.
literaryWorkInStory
Indicates that one literary work is referenced, featured, or embedded within the narrative of another story.
-
D.
literaryCollection
Indicates that one entity is a collection or compilation of literary works that includes or is associated with the other entity.
-
E.
literaryCenter
Indicates that a location functions as a primary hub or focal point for literary activity, such as writing, publishing, or literary culture.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8f52ca7881908704eef20228aed3 |
completed | April 14, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:15 a.m.