Triple
T30523726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NUTS region PL82 (Podkarpackie) |
E776771
|
entity |
| Predicate | locatedInMacroregion |
P92567
|
FINISHED |
| Object | Carpathian region |
—
|
NE NERFINISHED |
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: Carpathian region | Statement: [NUTS region PL82 (Podkarpackie), locatedInMacroregion, Carpathian region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInMacroregion Context triple: [NUTS region PL82 (Podkarpackie), locatedInMacroregion, Carpathian region]
-
A.
locatedInMetaregion
chosen
Indicates that one entity is geographically or administratively situated within a larger metaregion.
-
B.
belongsToEconomicMacroregion
Indicates that one economic region or area is part of, or classified within, a larger economic macroregion.
-
C.
locatedInMesoregion
Indicates that an entity is geographically situated within a specific mesoregion.
-
D.
belongsToMetropolitanRegion
Indicates that one geographic or administrative area is part of, or included within, a larger metropolitan region.
-
E.
locatedInStateOrRegion
Indicates that one entity is geographically situated within the boundaries of a specified state or region.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00bf5990e08190a8b633e237656564 |
completed | May 10, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_6a00beef4f5881909b00ac89e6af5902 |
completed | May 10, 2026, 5:22 p.m. |
Created at: April 29, 2026, 8:17 p.m.