Triple
T9026637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GameCube Broadband Adapter |
E216061
|
entity |
| Predicate | attachesVia |
P845
|
FINISHED |
| Object | GameCube expansion port |
—
|
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: GameCube expansion port | Statement: [GameCube Broadband Adapter, attachesVia, GameCube expansion port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attachesVia Context triple: [GameCube Broadband Adapter, attachesVia, GameCube expansion port]
-
A.
attachedTo
Indicates that one entity is physically or logically fastened, connected, or joined to another entity.
-
B.
appliesVia
Indicates that an action, rule, or effect is carried out, implemented, or achieved through a specified method, medium, or mechanism.
-
C.
connectsTo
chosen
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
D.
connectsPartOf
Indicates a relationship where one entity serves to link or join a component to the larger whole of which that component is a part.
-
E.
annexedBy
Indicates that one entity has been incorporated into and brought under the control or sovereignty of another entity.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7eb5b881908ace0c3327f06161 |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.