Triple
T12526280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIDI |
E299447
|
entity |
| Predicate | supportsOver |
P15794
|
FINISHED |
| Object | DIN cables |
—
|
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: DIN cables | Statement: [MIDI, supportsOver, DIN cables]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsOver Context triple: [MIDI, supportsOver, DIN cables]
-
A.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
-
B.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
C.
supportsAt
Indicates that one entity provides assistance, endorsement, or backing to another entity in a specific context, location, or point in time.
-
D.
supportsUse
chosen
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
E.
supportsReach
Indicates that one entity enables, facilitates, or maintains the ability of another entity to extend its influence, access, or coverage to additional targets or areas.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d9540d7b788190a0d57b098e90e491 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.