Triple
T11327613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julie d’Étanges |
E268261
|
entity |
| Predicate | hasCorrespondenceForm |
P98524
|
FINISHED |
| Object | letters |
—
|
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: letters | Statement: [Julie d’Étanges, hasCorrespondenceForm, letters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCorrespondenceForm Context triple: [Julie d’Étanges, hasCorrespondenceForm, letters]
-
A.
containsCorrespondenceWith
Indicates that one entity includes or holds correspondence (such as messages or communications) that is associated with or exchanged with another entity.
-
B.
hasCorrespondingAuthor
Indicates that an entity (such as a publication) is linked to the author who serves as the primary contact responsible for correspondence about it.
-
C.
hasDecisionForm
Indicates that an entity is associated with, or represented by, a particular decision document or formal decision record.
-
D.
hasWorkForm
Indicates that an entity is associated with a particular form, format, or mode in which its work or activity is carried out or expressed.
-
E.
hasForm
Indicates that one entity possesses, exhibits, or is characterized by a particular shape, structure, or configuration.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9e2253881909518cad0f12ef612 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:32 p.m.