Triple
T11507382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larsen |
E272819
|
entity |
| Predicate | categorizedInOnomasticsAs |
P22351
|
FINISHED |
| Object | Germanic-language 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: Germanic-language surname | Statement: [Larsen, categorizedInOnomasticsAs, Germanic-language surname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: categorizedInOnomasticsAs Context triple: [Larsen, categorizedInOnomasticsAs, Germanic-language surname]
-
A.
commonInOnomastics
Indicates that a name, term, or pattern frequently appears or is widely used within the study and practice of naming (onomastics).
-
B.
onomasticType
Indicates the specific kind or category of a name (e.g., personal, place, or other name type) that characterizes the naming relationship.
-
C.
nameGivesRiseTo
Indicates that one name, term, or designation leads to, causes, or results in the emergence or establishment of another.
-
D.
hasOnomasticField
chosen
Indicates a relationship where something is associated with a specific onomastic field, i.e., a domain or category related to names or naming conventions.
-
E.
oftenUsedAsNameFor
Indicates that something frequently serves as a name or designation for another entity.
- 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db43a648190be859bec2fe9f43b |
completed | April 10, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.