Triple
T26058825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WR |
E657199
|
entity |
| Predicate | regionWithinCountry |
P118149
|
FINISHED |
| Object | central 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: central Poland | Statement: [WR, regionWithinCountry, central Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionWithinCountry Context triple: [WR, regionWithinCountry, central Poland]
-
A.
regionOfHostCountry
Indicates that one entity is a geographic or administrative region belonging to, or located within, the specified host country.
-
B.
inCountrySubregion
chosen
Indicates that one location or entity is situated within a specific subregion of a country.
-
C.
meetsInCountrySubdivision
Indicates that two or more entities meet or have a meeting within a specific administrative subdivision of a country (such as a state, province, or region).
-
D.
refersToNationWithin
Indicates that one entity makes reference to, or is about, a specific nation that exists within a larger geopolitical or contextual scope.
-
E.
isWithinSingleCountry
Indicates that all referenced locations lie inside the borders of the same country.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 26, 2026, 7:14 p.m.