Triple
T14389250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BBC Micro |
E356798
|
entity |
| Predicate | expansionInterfaces |
P107285
|
FINISHED |
| Object | User 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: User Port | Statement: [BBC Micro, expansionInterfaces, User Port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionInterfaces Context triple: [BBC Micro, expansionInterfaces, User Port]
-
A.
expansionSystem
Indicates a relationship where a system undergoes or enables expansion, typically by increasing its scope, capacity, or components over time.
-
B.
hasExpansionInterface
chosen
Indicates that an entity provides or supports an interface through which it can be expanded or extended with additional components or functionality.
-
C.
expansionType
Indicates the specific manner or category by which something grows, extends, or increases in scope or size.
-
D.
expansionBus
Indicates a hardware connection through which a device can be attached to or communicate over an expansion bus.
-
E.
expansionSlots
Indicates that an entity provides one or more hardware expansion slots available for adding additional components or capabilities.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9029ef048190bdda5ee41618e720 |
completed | April 14, 2026, 7:06 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:16 a.m.