Triple
T26739764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canton of Appenzell Innerrhoden |
E674213
|
entity |
| Predicate | isHalfCanton |
P161183
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Canton of Appenzell Innerrhoden, isHalfCanton, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHalfCanton Context triple: [Canton of Appenzell Innerrhoden, isHalfCanton, true]
-
A.
isInHalf
Indicates that one entity is located within or belongs to a specified half or subdivision of another entity.
-
B.
hasCanton
Indicates that an entity is administratively divided into, or associated with, a specific canton.
-
C.
hasHalfTribe
Indicates a relationship where one entity possesses or is associated with a subgroup that constitutes half of a larger tribe.
-
D.
includesCanton
Indicates that a larger administrative or geographic entity contains or encompasses a specific canton within its boundaries.
-
E.
denotesCanton
Indicates that one entity is the canton (administrative subdivision) to which another entity belongs or with which it is associated.
- F. None of above. chosen
Provenance (4 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6184770d08190b6cb20a1cc91baf0 |
completed | May 2, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f6106d346c8190868489f36c65b6ec |
completed | May 2, 2026, 2:55 p.m. |
Created at: April 27, 2026, 3:48 a.m.