Triple
T25039158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ES-BI |
E627060
|
entity |
| Predicate | parentSubdivisionCode |
P61929
|
FINISHED |
| Object | ES |
—
|
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: ES | Statement: [ES-BI, parentSubdivisionCode, ES]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentSubdivisionCode Context triple: [ES-BI, parentSubdivisionCode, ES]
-
A.
primarySubdivisionOf
Indicates that one administrative or territorial unit is the main first-level subdivision within a larger political or geographic entity.
-
B.
hasSubdivisionCode
Indicates that an entity is associated with a specific code identifying one of its internal subdivisions (such as a state, province, or region).
-
C.
formerSubdivisionOf
Indicates that an entity once functioned as an administrative or territorial part of another entity but no longer holds that status.
-
D.
associatedCountrySubdivisionCode
chosen
Indicates the specific administrative region or subdivision code within a country that is linked to or relevant for the given entity.
-
E.
countrySubdivision
Indicates that one geopolitical region is an administrative or territorial subdivision of a larger country.
- 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 6:08 a.m.