Triple
T37421549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larsen (son of Lars) |
E929867
|
entity |
| Predicate | indicatesPaternalName |
P79536
|
FINISHED |
| Object | Lars |
—
|
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: Lars | Statement: [Larsen (son of Lars), indicatesPaternalName, Lars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indicatesPaternalName Context triple: [Larsen (son of Lars), indicatesPaternalName, Lars]
-
A.
isPaternalFamilyNameOf
Indicates that one name is the paternal (father’s-side) family surname borne by a given person.
-
B.
isPatronymicOrFamilyBased
Indicates that one entity’s name is derived from or based on the personal or family name of another entity.
-
C.
isPatronymicName
chosen
Indicates that a name is derived from a father’s or ancestor’s given name, typically signifying lineage or descent.
-
D.
patronymicOrMatronymic
Indicates that one entity’s name is derived from the father’s or mother’s name, expressing a parent-based naming relationship between the two entities.
-
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_69f76ebf0f288190ba198a78341613b8 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.