Triple
T9026636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GameCube Broadband Adapter |
E216061
|
entity |
| Predicate | physicalLocation |
P76038
|
FINISHED |
| Object | bottom of Nintendo GameCube console |
—
|
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: bottom of Nintendo GameCube console | Statement: [GameCube Broadband Adapter, physicalLocation, bottom of Nintendo GameCube console]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: physicalLocation Context triple: [GameCube Broadband Adapter, physicalLocation, bottom of Nintendo GameCube console]
-
A.
propertyLocation
Indicates the geographical place or address where a property is situated or found.
-
B.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
-
C.
objectLocation
chosen
Indicates that one entity is located at, in, or on another entity or spatial region.
-
D.
locationOfFacility
Indicates that a facility is situated at or associated with a specific geographic location.
-
E.
libraryLocation
Indicates the physical or organizational place where a library or its resources are situated.
- 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.