Triple
T36717554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kim Hansen |
E906953
|
entity |
| Predicate | hasTypicalNameOrder |
P179786
|
FINISHED |
| Object | given name followed by 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: given name followed by surname | Statement: [Kim Hansen, hasTypicalNameOrder, given name followed by surname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalNameOrder Context triple: [Kim Hansen, hasTypicalNameOrder, given name followed by surname]
-
A.
hasNameOrder
Indicates the specific sequence or arrangement in which the components of a name (e.g., given name, family name, titles) are ordered.
-
B.
areOrderedBy
Indicates that a set of items is arranged or sequenced according to a specified criterion or ordering rule.
-
C.
isGradeOfOrderNamed
Indicates that one entity is the grade or rank associated with a specific named order.
-
D.
hasCanonicalOrdering
Indicates that there is a standard, agreed-upon sequence in which the related elements should be arranged or considered.
-
E.
usedInFullNameOrder
chosen
Indicates that a particular ordering of name components is employed when constructing or displaying a person's full 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffacdf9f5c8190baef0245edfe87fc |
completed | May 9, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69ffac5e86e08190a1e6da0840a237ad |
completed | May 9, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:12 p.m.