Triple
T4088389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NL21 |
E87644
|
entity |
| Predicate | hasLowerLevelUnits |
P37103
|
FINISHED |
| Object | NUTS-3 regions within Overijssel |
—
|
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: NUTS-3 regions within Overijssel | Statement: [NL21, hasLowerLevelUnits, NUTS-3 regions within Overijssel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLowerLevelUnits Context triple: [NL21, hasLowerLevelUnits, NUTS-3 regions within Overijssel]
-
A.
hasLowerTier
Indicates that one entity is ranked, valued, or classified at a lower level or tier relative to another entity.
-
B.
hasHigherLevelSubdivision
chosen
Indicates that one administrative or organizational unit is contained within and subordinate to a larger, higher-level subdivision.
-
C.
hasMultipleLevels
Indicates that something is organized into more than one hierarchical or structural level.
-
D.
hasDivisionLevel
Indicates that one entity is associated with a specific hierarchical or organizational division level of another entity.
-
E.
hasParentUnit
Indicates that one unit is hierarchically contained within or belongs to another, higher-level unit.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefca9e9088190a97cb2ccb5d622f0 |
completed | March 9, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69aef909c9c88190b09d48dad325a83c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.