Triple
T30554529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gmina Sułkowice |
E777658
|
entity |
| Predicate | hasGeographicalLocation |
P185319
|
FINISHED |
| Object | southern 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: southern Poland | Statement: [Gmina Sułkowice, hasGeographicalLocation, southern Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeographicalLocation Context triple: [Gmina Sułkowice, hasGeographicalLocation, southern Poland]
-
A.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
-
B.
hasLocationCity
Indicates that an entity is situated in, occurs in, or is associated with a specific city as its location.
-
C.
isGeographicalEntity
Indicates that something exists as a distinct geographic feature, area, or place within physical space.
-
D.
hasGeocode
Indicates that an entity is associated with a specific geographic coordinate or coded location reference.
-
E.
containsGeographicalReferences
Indicates that something includes mentions or information about specific geographical locations or features.
- 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_69f2249e19108190a458ab446096bf22 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be520f148190ba200bf3dbf40656 |
completed | May 3, 2026, 9:29 p.m. |
Created at: April 29, 2026, 8:20 p.m.