Triple
T31513266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Botanique cultural complex |
E803996
|
entity |
| Predicate | openedAsCulturalCenter |
P49389
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [Botanique cultural complex, openedAsCulturalCenter, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsCulturalCenter Context triple: [Botanique cultural complex, openedAsCulturalCenter, 1980s]
-
A.
inauguratedAsCulturalCenter
Indicates that a place or facility was officially opened and designated to function as a cultural center.
-
B.
openedAsPerformingArtsCenter
Indicates that an entity was inaugurated or began operation specifically as a performing arts center.
-
C.
isCulturalCenter
Indicates that an entity serves as a primary hub or focal point for the cultural activities, expressions, and institutions of a community or region.
-
D.
isCulturalCenterFor
Indicates that one entity serves as a primary hub or focal point for the cultural activities, heritage, or identity of another entity.
-
E.
culturalCenterOpened
chosen
Indicates that a cultural center has begun operating or officially opened at a certain time or place.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 30, 2026, 9:51 p.m.