Triple
T27722682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Axelsson |
E699004
|
entity |
| Predicate | patronymicForm |
P42523
|
FINISHED |
| Object | "son of Axel" |
—
|
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: "son of Axel" | Statement: [Axelsson, patronymicForm, "son of Axel"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patronymicForm Context triple: [Axelsson, patronymicForm, "son of Axel"]
-
A.
patronymicName
Indicates that one entity’s name is derived from or based on the given name of a parent or ancestor, typically the father.
-
B.
patronymicSystem
Indicates a naming relationship where a person’s name is derived from or based on the given name of a parent or ancestor.
-
C.
patronymicOrigin
Indicates that one entity’s name is derived from the name of a father or paternal ancestor of another entity.
-
D.
patronymicSuffix
chosen
Indicates that one entity is a suffix added to a personal name to denote lineage or descent from another person, typically the father.
-
E.
patronymOrigin
Indicates that one entity’s name or designation is derived from the name of a father or paternal ancestor.
- 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 3:07 p.m.