Triple
T29720998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chanel suit |
E752053
|
entity |
| Predicate | rejectedFeature |
P167811
|
FINISHED |
| Object | corsetry |
—
|
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: corsetry | Statement: [Chanel suit, rejectedFeature, corsetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rejectedFeature Context triple: [Chanel suit, rejectedFeature, corsetry]
-
A.
rejectedRequirement
Indicates that a proposed requirement has been evaluated and explicitly not accepted or approved.
-
B.
rejectedConcept
Indicates that one entity has refused to accept, approve, or adopt a particular concept proposed by another entity.
-
C.
rejectedIn
Indicates that an entity or proposal was not accepted or was turned down within a specific context, process, or location.
-
D.
rejectedBy
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
E.
rejectedBecause
Indicates that one entity refused, dismissed, or did not accept another entity specifically due to a stated reason or cause.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672fa276881908992aa8271ec91be |
completed | May 2, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 28, 2026, 7:36 p.m.