Triple
T29044540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Schmidt |
E738094
|
entity |
| Predicate | nameUsageCategory |
P154642
|
FINISHED |
| Object | personal name |
—
|
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: personal name | Statement: [Alexander Schmidt, nameUsageCategory, personal name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameUsageCategory Context triple: [Alexander Schmidt, nameUsageCategory, personal name]
-
A.
nicknameCategory
Indicates that one entity is a nickname and the other entity is the category or type that this nickname belongs to.
-
B.
nameUsageRegister
Indicates the stylistic or social register in which a name is typically used (e.g., formal, informal, slang, archaic).
-
C.
isNameCategory
chosen
Indicates that something is classified as a particular category or type of name.
-
D.
codeNameCategory
Indicates that an entity’s code name belongs to or is classified under a particular category of code names.
-
E.
nameUsedIn
Indicates that a particular name is employed or referenced within a specified context, work, or usage setting.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6605fcf7c8190b387ad7b65c9f025 |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 10:04 a.m.