Triple
T37223048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACME products |
E922935
|
entity |
| Predicate | commonOutcomeFor |
P199477
|
FINISHED |
| Object | Wile E. Coyote's schemes fail |
—
|
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: Wile E. Coyote's schemes fail | Statement: [ACME products, commonOutcomeFor, Wile E. Coyote's schemes fail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonOutcomeFor Context triple: [ACME products, commonOutcomeFor, Wile E. Coyote's schemes fail]
-
A.
canonicalOutcome
Indicates that an event, process, or interaction leads to its standard, primary, or officially recognized result or consequence.
-
B.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
C.
preDeterminedOutcomes
Indicates that the outcomes of an event or process are fixed in advance and not influenced by subsequent actions or conditions.
-
D.
outcomeType
Indicates the specific category or nature of the result produced by an event, process, or action.
-
E.
supportedOutcomeOf
Indicates that one entity serves as evidence, backing, or justification for the outcome or result represented by another entity.
- 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_69f76ea7f0008190b31b8e30f3d05a71 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
| PDg | Predicate description generation | batch_69ff3b323a748190827165f1cb274141 |
completed | May 9, 2026, 1:48 p.m. |
Created at: May 3, 2026, 4:15 p.m.