Triple
T35929768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PL |
E1039125
|
entity |
| Predicate | associatedWithSubdivisionsStandard |
—
|
GENERATED |
| Object | ISO 3166-2:PL |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSubdivisionsStandard Context triple: [PL, associatedWithSubdivisionsStandard, ISO 3166-2:PL]
-
A.
associatedWithSubdivision
Indicates that one entity has a connection or linkage to a specific administrative or organizational subdivision.
-
B.
hasSubdivisionStandard
Indicates that a governing standard or specification defines how an entity is to be subdivided into smaller parts or units.
-
C.
countrySubdivisionStandardLink
chosen
Indicates a reference or link to the standard or authoritative specification that defines the country’s internal subdivisions.
-
D.
associatedCountrySubdivision
Indicates a relationship where an entity is linked to a specific administrative subdivision (such as a state, province, or region) within a country.
-
E.
hasSubdivision
Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
- F. None of above.
Provenance (1 batch)
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_69f76e23e4688190a5369138755138bf |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.