Triple
T16552399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NUTS classification |
E402103
|
entity |
| Predicate | coversTerritoryType |
P21438
|
FINISHED |
| Object | national level |
—
|
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: national level | Statement: [NUTS classification, coversTerritoryType, national level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversTerritoryType Context triple: [NUTS classification, coversTerritoryType, national level]
-
A.
territoryType
chosen
Indicates the specific kind or classification of a territory associated with an entity (e.g., country, region, zone, or jurisdiction type).
-
B.
includedTerritoryType
Indicates that one territory type is contained within, or forms part of, another territory type.
-
C.
definedTerritoryOf
Indicates that one entity specifies or establishes the official territorial boundaries or jurisdiction of another entity.
-
D.
refersToTerritory
Indicates that one entity designates, mentions, or is associated with a specific geographic area or territorial domain.
-
E.
usesTerritoryFor
Indicates that an entity employs or exploits a particular territory for a specific purpose, function, or activity.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fc6735481908b59bbf80fb3469b |
completed | April 18, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:15 a.m.