Triple
T6715486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perrette Bade |
E153255
|
entity |
| Predicate | hasGivenName |
P17
|
FINISHED |
| Object | Perrette |
E153255
|
NE 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: Perrette | Statement: [Perrette Bade, hasGivenName, Perrette]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Perrette Context triple: [Perrette Bade, hasGivenName, Perrette]
-
A.
Perrette Bade
chosen
Perrette Bade was the wife of the renowned 16th-century French printer and scholar Robert Estienne, associated with the influential Estienne family of humanist printers.
-
B.
Pierrette
Pierrette is a French feminine given name, traditionally considered the female form of Pierre.
-
C.
Françoise
Françoise is the given name of Louise de La Vallière, a 17th-century French noblewoman best known as a mistress of King Louis XIV.
-
D.
Armande
Armande is a French given name historically associated with figures in the performing arts, notably in 17th-century France.
-
E.
Renée
Renée is a feminine given name of French origin, commonly used in French-speaking countries and beyond.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c68809b4608190a2509ddb5ab87f05 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d1246b748190aed94e8ab8625f7e |
completed | March 27, 2026, 6:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7129975fc8190984132e0680b46c6 |
completed | March 27, 2026, 11:28 p.m. |
Created at: March 27, 2026, 2:07 p.m.