Triple
T7008970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State President of the Orange Free State |
E162530
|
entity |
| Predicate | nativeLanguageNameLanguage |
P52154
|
FINISHED |
| Object | Dutch |
—
|
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: Dutch | Statement: [State President of the Orange Free State, nativeLanguageNameLanguage, Dutch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeLanguageNameLanguage Context triple: [State President of the Orange Free State, nativeLanguageNameLanguage, Dutch]
-
A.
localLanguageName
chosen
Indicates the name of a language as it is written or referred to in its own local or native form.
-
B.
nativeLanguage
Indicates the language that a person or entity originally learned and uses as their primary or first language.
-
C.
alternateLanguageName
Indicates that an entity has an additional name or label in a different language from its primary or default name.
-
D.
languageOfWorkOrName
Indicates the language in which a work is created or a name is expressed.
-
E.
standardLanguageOf
Indicates that one entity serves as the officially recognized or commonly used standard language for another entity (such as a country, region, or organization).
- 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_69c6885928148190ae31909fbb5e9849 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc38039c8190ab420d62bb11b4d9 |
completed | March 27, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c790288190b7cbbaa4a5f9c91d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:33 p.m.