Triple
T5558987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amstrad CPC |
E145717
|
entity |
| Predicate | softwareDistribution |
P1486
|
FINISHED |
| Object | cassette tapes |
—
|
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: cassette tapes | Statement: [Amstrad CPC, softwareDistribution, cassette tapes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareDistribution Context triple: [Amstrad CPC, softwareDistribution, cassette tapes]
-
A.
distributionPackage
Indicates that one entity is a package or bundle used to distribute another entity (such as software, content, or resources).
-
B.
currentDistribution
Indicates the way something is presently allocated, spread, or shared among a set of entities or locations.
-
C.
allowsDistribution
Indicates that one entity grants permission for another entity to distribute or disseminate something (e.g., content, products, or data).
-
D.
softwareUpdateModel
Indicates that one entity serves as the model, specification, or type definition used to perform or describe a software update on another entity.
-
E.
distributionMethod
chosen
Indicates the means or channel through which something (such as a product, resource, or information) is delivered or made available to recipients.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020167afc8190b0c518907cd0d99b |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.