Triple
T27833215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiny Speck |
E703156
|
entity |
| Predicate | productOutcome |
P91959
|
FINISHED |
| Object | Glitch shut down |
—
|
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: Glitch shut down | Statement: [Tiny Speck, productOutcome, Glitch shut down]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productOutcome Context triple: [Tiny Speck, productOutcome, Glitch shut down]
-
A.
productionOutcome
chosen
Indicates the result or consequence produced by a given production process, activity, or event.
-
B.
productWith
Indicates a relationship where one entity is associated with, contains, or is offered together with another entity as a product.
-
C.
projectOutcome
Indicates the resulting state, impact, or consequences produced by carrying out a project.
-
D.
productIndication
Indicates that a product is intended, approved, or used for a particular purpose, condition, or application.
-
E.
productFor
Indicates that one entity is intended to be used by, with, or in relation to another entity as its product or offering.
- 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_69ef840b94b08190950a4f77296938b2 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 27, 2026, 5:57 p.m.