Triple
T19450395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atari Lynx |
E486599
|
entity |
| Predicate | cartridgeInsertion |
P135939
|
FINISHED |
| Object | top-loading |
—
|
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: top-loading | Statement: [Atari Lynx, cartridgeInsertion, top-loading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cartridgeInsertion Context triple: [Atari Lynx, cartridgeInsertion, top-loading]
-
A.
cartridge
Indicates that one entity is a cartridge associated with, contained in, or used by another entity.
-
B.
requiresCartridgeSlotOf
Indicates that one entity needs to use or be connected to the cartridge slot provided by another entity in order to function or be compatible.
-
C.
intendedCartridgeStandard
Indicates that an item is designed to be used with, or conform to, a particular cartridge standard.
-
D.
canEject
Indicates that one entity has the ability or permission to forcibly remove or expel another entity from a place, system, or context.
-
E.
cardSlots
Indicates a relationship where specific positions or slots are allocated or available for holding cards.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338caeb48190aeb1d511996984e3 |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:38 p.m.