Triple
T10643437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IE-L |
E250778
|
entity |
| Predicate | hasParentSubdivisionCategory |
P8622
|
FINISHED |
| Object | country |
—
|
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: country | Statement: [IE-L, hasParentSubdivisionCategory, country]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentSubdivisionCategory Context triple: [IE-L, hasParentSubdivisionCategory, country]
-
A.
hasParentSubdivisionSet
Indicates that an entity is associated with a set of higher-level subdivisions to which it belongs or from which it is derived.
-
B.
hasParentCategory
chosen
Indicates that an entity belongs to or is organized under a broader, more general category.
-
C.
hasSubdivisionCode
Indicates that an entity is associated with a specific code identifying one of its internal subdivisions (such as a state, province, or region).
-
D.
hasSubdivision
Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
-
E.
hasHigherLevelSubdivisionType
Indicates that one administrative or territorial subdivision type is hierarchically above another within a broader organizational structure.
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dfcf65fc81909a0c86daefaab1ab |
completed | April 8, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69d6dd83b114819098e84dc658e82d7e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:05 p.m.