Triple
T20190015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Family Computer Disk System |
E492957
|
entity |
| Predicate | serviceAssociatedWith |
P17741
|
FINISHED |
| Object | Disk Writer kiosks |
—
|
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: Disk Writer kiosks | Statement: [Family Computer Disk System, serviceAssociatedWith, Disk Writer kiosks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceAssociatedWith Context triple: [Family Computer Disk System, serviceAssociatedWith, Disk Writer kiosks]
-
A.
serviceWith
chosen
Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
-
B.
serviceFor
Indicates that one entity provides a service or performs functions on behalf of another entity.
-
C.
servicePatternOf
Indicates that one entity is the service pattern (e.g., schedule, routing, or operational configuration) that defines or characterizes how another service-related entity operates.
-
D.
serviceOf
Indicates that one entity performs, provides, or fulfills a function or duty on behalf of another entity.
-
E.
relatedService
Indicates that one service is connected or associated with another service in a relevant or dependent way.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad4d7a88190b70dfb74a2daafba |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:37 p.m.