Triple
T18384048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jürgen Schmidt |
E446532
|
entity |
| Predicate | nameComponentScript |
P63723
|
FINISHED |
| Object | Latin alphabet |
—
|
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: Latin alphabet | Statement: [Jürgen Schmidt, nameComponentScript, Latin alphabet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameComponentScript Context triple: [Jürgen Schmidt, nameComponentScript, Latin alphabet]
-
A.
scriptName
Indicates the name or title of a script associated with an entity, typically identifying which script is used, referenced, or executed in a given context.
-
B.
nativeNameScript
chosen
Indicates the writing system or script in which an entity’s native name is expressed.
-
C.
codenameComponent
Indicates that one entity serves as the codename or code-designation assigned to another entity as its component or identifying label.
-
D.
surnameScript
Indicates the writing system or script in which a person's surname is written.
-
E.
importName
Indicates that one entity brings another entity into a scope, module, or context under a specific name used for reference.
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e5179da1048190944398e229e7a4c1 |
completed | April 19, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:45 a.m.