Triple
T27667101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gobert-Bourgarel |
E697254
|
entity |
| Predicate | hasPaternalSurname |
P154434
|
FINISHED |
| Object | Gobert |
—
|
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: Gobert | Statement: [Gobert-Bourgarel, hasPaternalSurname, Gobert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPaternalSurname Context triple: [Gobert-Bourgarel, hasPaternalSurname, Gobert]
-
A.
isPaternalFamilyNameOf
chosen
Indicates that one name is the paternal (father’s-side) family surname borne by a given person.
-
B.
hasBaseSurname
Indicates that an entity’s surname is derived from, or fundamentally corresponds to, a specified base or canonical surname.
-
C.
hasSeptSurname
Indicates that an entity bears a surname associated with a particular sept (a family subgroup or clan division).
-
D.
hasPatronymicUse
Indicates that an entity uses a patronymic form of naming derived from a parent’s (typically the father’s) given name.
-
E.
hasPatronymicLine
Indicates a genealogical relationship where one entity’s name or lineage is derived from the father’s given name, forming a patronymic line.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 27, 2026, 2:39 p.m.