Triple
T25426431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altsys |
E637126
|
entity |
| Predicate | successorToProducts |
P146468
|
FINISHED |
| Object | Macromedia FreeHand |
—
|
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: Macromedia FreeHand | Statement: [Altsys, successorToProducts, Macromedia FreeHand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorToProducts Context triple: [Altsys, successorToProducts, Macromedia FreeHand]
-
A.
successorOrRelatedProduct
chosen
Indicates that one product is a successor to, replacement for, or closely related evolution of another product.
-
B.
successorManufacturer
Indicates that one manufacturer has taken over, replaced, or continued the role or operations of another manufacturer as its successor.
-
C.
successorInMarket
Indicates that one entity has taken over or followed another in serving the same market or customer base.
-
D.
successorModel
Indicates that one model is the direct follow-up or replacement for another earlier model.
-
E.
successorBrandOwner
Indicates that one brand owner has taken over ownership or control of a brand from a previous brand owner, acting as its legal or commercial successor.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 21, 2026, 1:57 p.m.