Triple
T21442514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CED |
E528970
|
entity |
| Predicate | reasonForCommercialFailure |
P77548
|
FINISHED |
| Object | late market entry |
—
|
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: late market entry | Statement: [CED, reasonForCommercialFailure, late market entry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForCommercialFailure Context triple: [CED, reasonForCommercialFailure, late market entry]
-
A.
failureCause
chosen
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
-
B.
reasonForIneffectiveness
Indicates that one entity specifies the cause or explanation for why another entity is ineffective or fails to achieve its intended effect.
-
C.
commercialSuccessIn
Indicates that something has achieved notable commercial success within a specified market, region, or domain.
-
D.
reasonForDiscontinuation
Indicates that one entity specifies the cause or justification for stopping, ending, or withdrawing another entity, process, or activity.
-
E.
reasonForDecline
Indicates the explanation or cause given for why something was rejected, reduced, or not accepted.
- 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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b7044a3881908a7fe26f26c92762 |
completed | April 22, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:05 p.m.