Triple
T24314645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haraldur |
E612771
|
entity |
| Predicate | followsPatronymicSystem |
P58880
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Haraldur, followsPatronymicSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsPatronymicSystem Context triple: [Haraldur, followsPatronymicSystem, yes]
-
A.
patronymicSystem
Indicates a naming relationship where a person’s name is derived from or based on the given name of a parent or ancestor.
-
B.
hasPatronymicUse
chosen
Indicates that an entity uses a patronymic form of naming derived from a parent’s (typically the father’s) given name.
-
C.
usesPatronymicPrefix
Indicates that one entity forms or refers to a person’s name using a patronymic prefix derived from their father’s (or ancestor’s) name.
-
D.
isPatronymicSurname
Indicates that a surname is derived from the given name of a father or male ancestor, typically signifying "son/daughter of" that person.
-
E.
isPatronymicIn
Indicates that a name or term is used as a patronymic within a specified language, culture, or naming system.
- 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_69e2d7da491c8190b6e6218af50923db |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292a6377081909bf7fe66a8719d32 |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:46 a.m.