Triple
T27833290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fog Creek Software |
E703158
|
entity |
| Predicate | laterBrandedAs |
P6643
|
FINISHED |
| Object | Glitch |
—
|
NE NERFINISHED |
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 | Statement: [Fog Creek Software, laterBrandedAs, Glitch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterBrandedAs Context triple: [Fog Creek Software, laterBrandedAs, Glitch]
-
A.
laterBrandOf
Indicates that one brand is a subsequent or successor brand to another, coming into use at a later time.
-
B.
namedBrandAfter
Indicates that one brand has been given a name derived from or in honor of another entity.
-
C.
formerBrand
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
-
D.
successorBranding
chosen
Indicates that one brand has replaced or continued another brand as its subsequent or updated identity.
-
E.
laterChannelBrand
Indicates that one channel brand succeeds or replaces another channel brand at a later point in time.
- 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_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: April 27, 2026, 5:57 p.m.