Triple
T21782662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Walloon |
E537750
|
entity |
| Predicate | isVarietyOfLanguageWithISO639_3Code |
P84576
|
FINISHED |
| Object | wln |
—
|
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: wln | Statement: [Central Walloon, isVarietyOfLanguageWithISO639_3Code, wln]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isVarietyOfLanguageWithISO639_3Code Context triple: [Central Walloon, isVarietyOfLanguageWithISO639_3Code, wln]
-
A.
hasISO6393Code
Indicates that a language or linguistic entity is associated with a specific ISO 639-3 three-letter language code.
-
B.
haveISO639Code
Indicates that a language or linguistic entity is associated with a specific ISO 639 standardized language code.
-
C.
hasLinguisticVariety
chosen
Indicates that one entity possesses or exhibits a particular linguistic variety in relation to another entity or context.
-
D.
ISO639-3CodeOfLanguage
Indicates that one entity is the ISO 639-3 three-letter language code assigned to the language represented by the other entity.
-
E.
hasISO639LanguageCodeForMajorLanguage
Indicates that an entity is associated with a primary or major language identified by a specific ISO 639 language code.
- 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_69e0c47198f881908cb0d237266c10e9 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0462ed0ec81908833e18c164e8b5c |
completed | April 28, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:52 p.m.