Triple
T36740499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WRS |
E907595
|
entity |
| Predicate | associatedCityCenter |
P25976
|
FINISHED |
| Object | Warsaw city centre |
E237933
|
NE 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: Warsaw city centre | Statement: [WRS, associatedCityCenter, Warsaw city centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCityCenter Context triple: [WRS, associatedCityCenter, Warsaw city centre]
-
A.
notableCityCenter
Indicates that a location serves as a prominent or significant central area within a city.
-
B.
isTownCenterOf
Indicates that a location functions as the central, primary area or hub of a specified town.
-
C.
isTransportCenterOf
Indicates that a location functions as a primary hub or central node for transportation activities serving another area or network.
-
D.
isSocialCenterOf
Indicates that one entity serves as the primary gathering place or hub for social activities and interactions for another entity or group.
-
E.
hasCityCentreLocation
chosen
Indicates that something is located in, or directly associated with, the central area of a city.
- F. None of above.
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_69f76e75aa6881909b844d00a3888ee5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e1610bdd081909af6c5352fab5068 |
completed | June 26, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.