Triple
T11903481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cristóbal Balenciaga |
E283214
|
entity |
| Predicate | closedCoutureHouse |
P102153
|
FINISHED |
| Object | 1968 |
—
|
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: 1968 | Statement: [Cristóbal Balenciaga, closedCoutureHouse, 1968]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedCoutureHouse Context triple: [Cristóbal Balenciaga, closedCoutureHouse, 1968]
-
A.
closedFor
Indicates that an entity is not available or accessible for use, entry, or operation during a specified time, condition, or reason.
-
B.
closureType
Indicates the specific manner or condition in which something is closed, completed, or terminated within a process or relationship.
-
C.
isFashionCenterFor
Indicates that something serves as a primary hub or focal point for fashion-related activities, influence, or industry.
-
D.
closedDuring
Indicates that an entity is not open or available for use during a specified time period or under certain conditions.
-
E.
closedAsFoundry
Indicates that an entity has been shut down or decommissioned specifically in its role or status as a foundry.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8dd1792648190853f15fbf217eebd |
completed | April 10, 2026, 11:20 a.m. |
| PD | Predicate disambiguation | batch_69d8bb2fca4481909893f3428b0871ac |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8d399d58c81908dab572aa82426d7 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 8, 2026, 9:44 p.m.