Triple
T2391630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palace of Culture and Science |
E48955
|
entity |
| Predicate | notableEventVenueFor |
P36296
|
FINISHED |
| Object | concerts |
—
|
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: concerts | Statement: [Palace of Culture and Science, notableEventVenueFor, concerts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEventVenueFor Context triple: [Palace of Culture and Science, notableEventVenueFor, concerts]
-
A.
eventLocationOfNotableActivity
chosen
Indicates that a location is the place where a notable or significant activity or event involving the related entity occurred.
-
B.
notableRecordingVenueFor
Indicates that a venue is particularly recognized or distinguished as the place where a specific recording was made.
-
C.
notableEventResponse
Indicates a response, reaction, or consequence that occurs as a result of a notable event.
-
D.
celebratedEvent
Indicates that an entity has been honored, commemorated, or festively observed as a special event.
-
E.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
- 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_69a88aa5f63081908d07fd302029fcbd |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc87587708190a7f2bc473a898bc2 |
completed | March 7, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69abc5a1b5748190b4cd8989700f4dd2 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.