Triple
T2846862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silesian language |
E63001
|
entity |
| Predicate | hasCensusCategory |
P13001
|
FINISHED |
| Object | język śląski |
—
|
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: język śląski | Statement: [Silesian language, hasCensusCategory, język śląski]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCensusCategory Context triple: [Silesian language, hasCensusCategory, język śląski]
-
A.
censusDefinedAs
chosen
Indicates that one entity is formally specified, characterized, or classified by another according to census definitions or criteria.
-
B.
basedOnCensusYear
Indicates that something (such as data, a decision, or a classification) is derived from or determined using information from a specific census year.
-
C.
hasDemographic
Indicates that an entity is associated with or characterized by a particular demographic group or attribute.
-
D.
censusRegion
Indicates the broader census-defined geographic region in which an entity (such as a place or population unit) is located or classified.
-
E.
hasRankCategory
Indicates that an entity is assigned to a particular rank-based classification or level within an ordered hierarchy.
- 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf3ebbac819090e2bf98ed9fbd02 |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd0e86808190bcefffafbd3cd441 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.