Triple
T36686173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stegny |
E905821
|
entity |
| Predicate | partOfCityDistrictStructure |
P119773
|
FINISHED |
| Object | southern Warsaw |
—
|
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: southern Warsaw | Statement: [Stegny, partOfCityDistrictStructure, southern Warsaw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfCityDistrictStructure Context triple: [Stegny, partOfCityDistrictStructure, southern Warsaw]
-
A.
inCityDistrict
Indicates that one entity is located within the boundaries of a specific city district.
-
B.
targetCityDistrict
Indicates that one entity is a specific city district that serves as the target or destination in relation to another entity.
-
C.
hasCityDistrictAlong
Indicates that a city district is located along or adjacent to a specified linear feature, such as a road, river, or coastline.
-
D.
partOfUrbanLayout
chosen
Indicates that one entity is a component or constituent element within the overall structure or organization of an urban area.
-
E.
cityDistrictFeature
Indicates that a specific feature or attribute is associated with, located in, or characteristic of a particular city district.
- 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a012594c27081908c80f0e0e6010290 |
completed | May 11, 2026, 12:40 a.m. |
| PD | Predicate disambiguation | batch_6a01252350548190b1df9edc9e581e91 |
completed | May 11, 2026, 12:38 a.m. |
Created at: May 3, 2026, 4:12 p.m.