Triple
T3405674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aubert |
E71764
|
entity |
| Predicate | hasSurnameType |
P49105
|
FINISHED |
| Object | patronymic surname |
—
|
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: patronymic surname | Statement: [Aubert, hasSurnameType, patronymic surname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurnameType Context triple: [Aubert, hasSurnameType, patronymic surname]
-
A.
hasBaseSurname
Indicates that an entity’s surname is derived from, or fundamentally corresponds to, a specified base or canonical surname.
-
B.
hasComponentSurname
Indicates that an entity’s full name includes a specified surname as one of its component parts.
-
C.
isOccupationalSurname
Indicates that a surname originates from or is derived from a person’s occupation or trade.
-
D.
hasMarriedSurname
Indicates that a person’s current surname is the one they adopted through marriage.
-
E.
hasTypeName
Indicates that an entity is associated with a specific type name used to classify or identify its kind.
- 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_69ad85aac4808190a092c9cc8911f584 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb8ec68c88190913df5f6cafad9e9 |
completed | March 8, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69adadfa73ac8190a163f93e88d217f8 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb21a437c81908bca88d5e123d744 |
completed | March 8, 2026, 5:30 p.m. |
Created at: March 8, 2026, 3:15 p.m.