Triple
T17003871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NUTS-1 region NL2 |
E412517
|
entity |
| Predicate | isHigherLevelOf |
P4476
|
FINISHED |
| Object | NUTS-2 region NL21 |
—
|
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-2 region NL21 | Statement: [NUTS-1 region NL2, isHigherLevelOf, NUTS-2 region NL21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHigherLevelOf Context triple: [NUTS-1 region NL2, isHigherLevelOf, NUTS-2 region NL21]
-
A.
hasHigherClass
chosen
Indicates that one entity belongs to a higher rank, level, or category in a hierarchy than another entity.
-
B.
isHigherThan
Indicates that one entity has a greater value, level, or position than another entity.
-
C.
hasHigherLevelRegion
Indicates that one region is geographically or administratively contained within and subordinate to a larger, higher-level region.
-
D.
hasHigherLevelPrinciple
Indicates that one principle functions at a more abstract, overarching, or governing level in relation to another principle.
-
E.
hasLevel
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d380f968819097b59e7bac333ea4 |
completed | April 18, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69e35d552bc08190af17ef7659e094ef |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.