Triple
T2302817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dublin Region |
E51769
|
entity |
| Predicate | NUTSLevel |
P2415
|
FINISHED |
| Object | NUTS 3 |
—
|
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 | Statement: [Dublin Region, NUTSLevel, NUTS 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NUTSLevel Context triple: [Dublin Region, NUTSLevel, NUTS 3]
-
A.
NUTSRegionCode
chosen
Indicates the classification of an entity according to the NUTS (Nomenclature of Territorial Units for Statistics) regional coding system used for statistical regions.
-
B.
hasHigherLevelSubdivision
Indicates that one administrative or organizational unit is contained within and subordinate to a larger, higher-level subdivision.
-
C.
hasHighestLevelSubdivisionOf
Indicates that one entity is the topmost or primary first-level administrative or territorial subdivision of another entity.
-
D.
hasProvinceLevelUnit
Indicates that one administrative or territorial entity possesses or contains a sub-unit at the province (or equivalent) level.
-
E.
jurisdictionLevel
Indicates the scope or tier of authority under which an entity or action is legally governed or regulated.
- 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_69a88b0a9f248190bcff941463d8f65a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcbabf01081908db3b42bc7c60444 |
completed | March 7, 2026, 6:54 a.m. |
| PD | Predicate disambiguation | batch_69abc58ad33c8190b8d68af41b6f5e07 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.