Triple
T1328647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carré Theatre |
E28388
|
entity |
| Predicate | cityCulturalRole |
P8234
|
FINISHED |
| Object | major venue in Amsterdam cultural life |
—
|
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: major venue in Amsterdam cultural life | Statement: [Carré Theatre, cityCulturalRole, major venue in Amsterdam cultural life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityCulturalRole Context triple: [Carré Theatre, cityCulturalRole, major venue in Amsterdam cultural life]
-
A.
hasCulturalRole
Indicates that an entity fulfills or is assigned a specific function, position, or significance within a cultural, social, or traditional context.
-
B.
cityOfInfluence
Indicates the city that significantly shapes, impacts, or exerts influence over a given entity.
-
C.
hasCulturalSignificanceFor
Indicates that something holds particular cultural meaning, value, or importance for a specified group or community.
-
D.
hasCulturalFunction
Indicates that something serves a particular role, purpose, or function within a culture or cultural context.
-
E.
hasCityRole
chosen
Indicates that an entity holds or is assigned a specific role, function, or status within a particular 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1c1d8188190b15a641a08345adc |
completed | March 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69a4beef6a188190996f8775bdda8f6c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.