Triple
T31676261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Richter |
E808406
|
entity |
| Predicate | hasNameOrderConvention |
P28784
|
FINISHED |
| Object | Western name order |
—
|
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: Western name order | Statement: [Thomas Richter, hasNameOrderConvention, Western name order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameOrderConvention Context triple: [Thomas Richter, hasNameOrderConvention, Western name order]
-
A.
hasNameOrder
chosen
Indicates the specific sequence or arrangement in which the components of a name (e.g., given name, family name, titles) are ordered.
-
B.
isNamedAccordingTo
Indicates that one entity receives its name based on, or in accordance with, another entity, rule, or naming convention.
-
C.
isGradeOfOrderNamed
Indicates that one entity is the grade or rank associated with a specific named order.
-
D.
hasProperName
Indicates that an entity is associated with a specific proper name used to uniquely identify it.
-
E.
usedInFullNameOrder
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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: April 30, 2026, 11:03 p.m.