Triple
T4317562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flemish Community |
E96428
|
entity |
| Predicate | nativeLanguageCode |
P151
|
FINISHED |
| Object | nl |
—
|
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: nl | Statement: [Flemish Community, nativeLanguageCode, nl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeLanguageCode Context triple: [Flemish Community, nativeLanguageCode, nl]
-
A.
nativeLanguage
chosen
Indicates the language that a person or entity originally learned and uses as their primary or first language.
-
B.
primaryLanguageOf
Indicates that a specified language is the main or official language used by a particular entity (such as a person, organization, or region).
-
C.
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).
-
D.
languageFamilyCode
Indicates the language family to which a given language belongs, represented by a standardized code.
-
E.
localLanguageName
Indicates the name of a language as it is written or referred to in its own local or native form.
- 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_69b345422aac81909ddbadae437d122e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b350f733888190866611fcdea97a5f |
completed | March 12, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69b34f4a07b08190a06ada0d9cbb14fb |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:12 p.m.