Triple
T2068747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roussel |
E45966
|
entity |
| Predicate | isOfOnomasticType |
P12903
|
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: [Roussel, isOfOnomasticType, patronymic surname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOfOnomasticType Context triple: [Roussel, isOfOnomasticType, patronymic surname]
-
A.
hasOnomasticField
Indicates a relationship where something is associated with a specific onomastic field, i.e., a domain or category related to names or naming conventions.
-
B.
commonInOnomastics
Indicates that a name, term, or pattern frequently appears or is widely used within the study and practice of naming (onomastics).
-
C.
hasAppellationType
chosen
Indicates that an entity’s name or title is associated with a specific category or type of appellation.
-
D.
isMatronymicOf
Indicates that one entity is a name or designation derived from the mother of another entity, typically used as that entity’s family or identifying name.
-
E.
nameType
Indicates the specific category or type of a name associated with an entity (e.g., legal name, nickname, alias, or preferred name).
- 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_69a8891b38288190abd572ccad9b6928 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9f51a008190aead0173a9289204 |
completed | March 7, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69abb7aee9b48190999620176e3a6ee2 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:41 p.m.