Triple
T30249365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zarzecze, Galicia |
E769152
|
entity |
| Predicate | historicalRegionNowDividedBetween |
P198386
|
FINISHED |
| Object | Poland |
—
|
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: Poland | Statement: [Zarzecze, Galicia, historicalRegionNowDividedBetween, Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalRegionNowDividedBetween Context triple: [Zarzecze, Galicia, historicalRegionNowDividedBetween, Poland]
-
A.
historicalRegionNowInCountry
Indicates that a historical region is currently located within the borders or jurisdiction of a specified modern country.
-
B.
historicalRegion
Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
-
C.
historicallyDividedInto
Indicates that an entity was separated into multiple distinct parts or regions during a past historical period.
-
D.
historicalRegionPartlyIn
Indicates that a historical region is located partly, but not entirely, within a specified larger area or territory.
-
E.
historicalAdministrativeRegionName
Indicates the name assigned to an administrative region as it existed during a specific historical period.
- F. None of above. chosen
Provenance (4 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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
| PDg | Predicate description generation | batch_69fee0b03a0c81909117dc5915d77295 |
completed | May 9, 2026, 7:22 a.m. |
Created at: April 29, 2026, 7:40 p.m.