Triple
T18460633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 3166-2:LI |
E451021
|
entity |
| Predicate | subdivisionTypeName |
P111252
|
FINISHED |
| Object | Gemeinde |
—
|
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: Gemeinde | Statement: [ISO 3166-2:LI, subdivisionTypeName, Gemeinde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subdivisionTypeName Context triple: [ISO 3166-2:LI, subdivisionTypeName, Gemeinde]
-
A.
subdivisionType0
Indicates that the referenced entity is classified as the primary (level 0) type of administrative or territorial subdivision within a larger jurisdiction.
-
B.
subdivisionNameType
chosen
Indicates the type or category of a named geographic or administrative subdivision (e.g., province, state, district) associated with an entity.
-
C.
subdivisionName0
Indicates the name assigned to the first (primary) subdivision or sub-unit associated with an entity.
-
D.
hasTypeOfSubdivision
Indicates that one administrative or territorial unit is classified as a specific kind or category of subdivision.
-
E.
subdivisionName1
Indicates that the first named subdivision is identified by a specific name or designation within a larger geographic or organizational 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a7e65bc8190a824bce5b322c3de |
completed | April 19, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:33 a.m.