Triple
T30782558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGI |
E783856
|
entity |
| Predicate | regionOfAllocation |
P65949
|
FINISHED |
| Object | north-eastern Poland |
—
|
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: north-eastern Poland | Statement: [NGI, regionOfAllocation, north-eastern Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfAllocation Context triple: [NGI, regionOfAllocation, north-eastern Poland]
-
A.
occupiedRegion
Indicates that an entity has taken control of and is currently holding a specific geographic area or region.
-
B.
regionOfAssociation
Indicates a broader geographic or spatial area with which an entity is functionally, contextually, or organizationally associated.
-
C.
regionFrom
Indicates that something originates from, is derived from, or is associated with a particular geographic or administrative region.
-
D.
allocation
chosen
Indicates the distribution or assignment of resources, responsibilities, or items among entities according to some rule or plan.
-
E.
bulkRegion
Indicates a relationship where something pertains to, occupies, or defines a primary mass or volume region of an object or space, as opposed to its surface or boundary.
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: April 29, 2026, 8:41 p.m.