Triple
T3356357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District VII (Erzsébetváros) |
E70613
|
entity |
| Predicate | hasCulturalSiteType |
P47444
|
FINISHED |
| Object | synagogues |
—
|
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: synagogues | Statement: [District VII (Erzsébetváros), hasCulturalSiteType, synagogues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCulturalSiteType Context triple: [District VII (Erzsébetváros), hasCulturalSiteType, synagogues]
-
A.
culturalSite
Indicates that one entity is recognized or designated as a cultural site associated with or located in relation to another entity.
-
B.
containsCulturalHeritageSite
Indicates that a place or area includes within its boundaries at least one recognized cultural heritage site.
-
C.
hasArchaeologicalSiteType
Indicates that an entity is classified as, or associated with, a specific type or category of archaeological site.
-
D.
hasCulturalFacilityType
Indicates that an entity has or is associated with a specific type of cultural facility (such as a museum, theater, or gallery).
-
E.
hasCulturalProperty
Indicates that something possesses or is associated with a cultural attribute, value, or characteristic.
- 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_69ad85a660c48190998489309a3b4869 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb242d4988190bbac993df587936d |
completed | March 8, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69ada42fbe7c8190b9f185b5ab985f17 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada52716ec81908e89688a81039394 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:13 p.m.