Triple
T16552450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NUTS |
E402104
|
entity |
| Predicate | NUTS3Definition |
P18792
|
FINISHED |
| Object | small regions for specific diagnoses |
—
|
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: small regions for specific diagnoses | Statement: [NUTS, NUTS3Definition, small regions for specific diagnoses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NUTS3Definition Context triple: [NUTS, NUTS3Definition, small regions for specific diagnoses]
-
A.
NUTSRegionCode
Indicates the classification of an entity according to the NUTS (Nomenclature of Territorial Units for Statistics) regional coding system used for statistical regions.
-
B.
nestType
Indicates the type or kind of nest associated with or used by an entity.
-
C.
coreDefinition
Indicates the fundamental, central meaning or essence that defines something at its most basic level.
-
D.
divisionDefinedBy
Indicates that a division or partition is established or characterized according to a specified rule, criterion, or defining entity.
-
E.
thirdTier
chosen
Indicates that an entity occupies a third level or rank within a hierarchical structure or classification.
- 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.