Triple
T5601739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZX Spectrum |
E147134
|
entity |
| Predicate | expansionInterface |
P31273
|
FINISHED |
| Object | rear edge 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: rear edge connector | Statement: [ZX Spectrum, expansionInterface, rear edge connector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionInterface Context triple: [ZX Spectrum, expansionInterface, rear edge connector]
-
A.
expansionType
Indicates the specific manner or category by which something grows, extends, or increases in scope or size.
-
B.
expansionAdded
Indicates that an additional component, feature, or content has been incorporated into an existing entity or system.
-
C.
expandsIn
Indicates that one entity grows, spreads, or extends its presence or influence within the space, scope, or context defined by another entity.
-
D.
expansionProject
Indicates a project whose primary purpose is to enlarge, extend, or increase the capacity, scope, or reach of something.
-
E.
expansionBus
chosen
Indicates a hardware connection through which a device can be attached to or communicate over an expansion bus.
- 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_69c009043d648190a7af89698ccf1e3e |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020dbd6dc8190ba011876c205754e |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1890ec8190b9e6fa488792e4d4 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.