Triple
T27498112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anne de Joyeuse |
E694070
|
entity |
| Predicate | nobleTitleCreationBy |
P154954
|
FINISHED |
| Object | Henry III of France |
—
|
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: Henry III of France | Statement: [Anne de Joyeuse, nobleTitleCreationBy, Henry III of France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleTitleCreationBy Context triple: [Anne de Joyeuse, nobleTitleCreationBy, Henry III of France]
-
A.
nobleTitleCreationDate
Indicates the date on which a particular noble title was formally created or granted.
-
B.
aristocraticTitleCreatedFrom
Indicates that an aristocratic title originates from, or was formally established based on, another specified source title or entity.
-
C.
nobleTitleGranted
chosen
Indicates that a noble title has been formally conferred upon an entity by an authorized grantor or authority.
-
D.
aristocraticTitleCreationReason
Indicates the reason or circumstance under which an aristocratic title was created or granted.
-
E.
nobleTitleStartDate
Indicates the date on which an entity first acquired or began holding a particular noble title.
- 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62ec0c9888190a7f0de2aa4d1d0b1 |
completed | May 2, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:09 p.m.