Triple
T27999227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Synagogue – Center of Contemporary Art |
E707101
|
entity |
| Predicate | situatedInCityCenter |
P25976
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Synagogue – Center of Contemporary Art, situatedInCityCenter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: situatedInCityCenter Context triple: [Synagogue – Center of Contemporary Art, situatedInCityCenter, true]
-
A.
hasCityCentreLocation
chosen
Indicates that something is located in, or directly associated with, the central area of a city.
-
B.
hasMonumentInCenter
Indicates that a place or area has a monument located at its central point or main focal area.
-
C.
cityCentreAccess
Indicates whether an entity has access to, or is reachable within, the central area of a city.
-
D.
hasCoordinateInCityCentreApprox
Indicates that an entity’s location is approximately within the central area of a city, based on its geographic coordinates.
-
E.
notableCityCenter
Indicates that a location serves as a prominent or significant central area within a city.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 7:55 p.m.