Triple
T24271359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CLP |
E605285
|
entity |
| Predicate | regionSubdivisionOf |
P55508
|
FINISHED |
| Object | Lower Saxony |
—
|
NE NERFINISHED |
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: Lower Saxony | Statement: [CLP, regionSubdivisionOf, Lower Saxony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionSubdivisionOf Context triple: [CLP, regionSubdivisionOf, Lower Saxony]
-
A.
countrySubdivision
Indicates that one geopolitical region is an administrative or territorial subdivision of a larger country.
-
B.
realmSubdivision
Indicates a hierarchical relationship where one realm is a constituent subdivision or part of a larger realm.
-
C.
countrySubdivisionType
Indicates the specific type or category of an administrative or territorial subdivision within a country (e.g., state, province, region).
-
D.
formerSubdivisionOf
Indicates that an entity once functioned as an administrative or territorial part of another entity but no longer holds that status.
-
E.
regionDivision
chosen
Indicates a hierarchical or organizational subdivision relationship where one region is partitioned into smaller constituent regions.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28d59e0808190a1048e4e2e5689f3 |
completed | April 29, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.