Triple
T20610377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Game Link Cable |
E506431
|
entity |
| Predicate | cableEndShape |
P140747
|
FINISHED |
| Object | proprietary Nintendo connector |
—
|
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: proprietary Nintendo connector | Statement: [Game Link Cable, cableEndShape, proprietary Nintendo connector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cableEndShape Context triple: [Game Link Cable, cableEndShape, proprietary Nintendo connector]
-
A.
cableEnd
Indicates that one entity represents an endpoint or terminal position of a cable in relation to another entity.
-
B.
cableType
Indicates the specific kind or category of cable associated with or used by an entity.
-
C.
hasCableArrangement
Indicates that one entity is connected to or equipped with another entity through a specific configuration or layout of cables.
-
D.
hasCabAtEachEnd
Indicates that something (typically a vehicle or train) has a cab located at both of its ends.
-
E.
isPartOfNetworkEnd
Indicates that an entity functions as a terminal or boundary component within a larger network structure or system.
- F. None of above. chosen
Provenance (4 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aad6f53481908fb242947dda7028 |
completed | April 20, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:41 a.m.