Triple
T27074338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCM/70 |
E685415
|
entity |
| Predicate | hasPeripheralInterface |
P34297
|
FINISHED |
| Object | cassette interface |
—
|
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 interface | Statement: [MCM/70, hasPeripheralInterface, cassette interface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeripheralInterface Context triple: [MCM/70, hasPeripheralInterface, cassette interface]
-
A.
isPeripheralFor
Indicates that one entity functions as a peripheral or auxiliary component in relation to another primary system or device.
-
B.
hasCommunicationInterface
chosen
Indicates that one entity provides or supports a specific means or channel through which it can communicate or exchange data with another entity or system.
-
C.
hasPeripheralPattern
Indicates that one entity exhibits or is characterized by a pattern located at or toward the periphery or outer boundary of another entity.
-
D.
peripheralType
Indicates the specific category or kind of peripheral device associated with or used by an entity.
-
E.
hasSurfaceConnection
Indicates that two entities are directly connected or in contact at their surfaces, allowing interaction or continuity between them.
- 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 27, 2026, 8:30 a.m.