Triple
T28333022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Divine Sarah |
E717583
|
entity |
| Predicate | refersToByBirthName |
P18679
|
FINISHED |
| Object | Henriette-Rosine Bernard |
—
|
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: Henriette-Rosine Bernard | Statement: [The Divine Sarah, refersToByBirthName, Henriette-Rosine Bernard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToByBirthName Context triple: [The Divine Sarah, refersToByBirthName, Henriette-Rosine Bernard]
-
A.
appliesToPersonBirthName
chosen
Indicates that the referenced value is used as the birth name of the specified person.
-
B.
bearerBirthNameOf
Indicates that one entity is the birth name originally given to and borne by another entity.
-
C.
refersToPersonBornOn
Indicates that one entity makes reference to, or is associated with, a specific person who was born on a given date.
-
D.
familyNameRefersTo
Indicates that a specified family name designates or refers to a particular person, group, or lineage.
-
E.
refersToPerson
Indicates that one entity is making reference to, mentioning, or pointing specifically to a particular person.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 28, 2026, 12:33 a.m.