Triple
T29456680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alice chip |
E747119
|
entity |
| Predicate | primaryBusConnection |
P32414
|
FINISHED |
| Object | Amiga system bus |
—
|
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: Amiga system bus | Statement: [Alice chip, primaryBusConnection, Amiga system bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBusConnection Context triple: [Alice chip, primaryBusConnection, Amiga system bus]
-
A.
primaryBus
chosen
Indicates that one entity functions as the main or principal bus associated with another entity within a system or configuration.
-
B.
primaryConnections
Indicates that there exists a main or most significant relationship or linkage between entities, distinguishing these connections from secondary or peripheral ones.
-
C.
connectsToBusAt
Indicates that one entity has an access or transfer point where it links to a bus service at a specific location or stop.
-
D.
primaryHubFor
Indicates that one entity serves as the main central hub or core point of coordination for another entity or set of entities.
-
E.
primaryRailLinkFor
Indicates that one entity serves as the main or principal rail connection or route for 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_69f0bd4125f88190b56104591351619c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a013632a3048190b05716d803f34716 |
completed | May 11, 2026, 1:51 a.m. |
| PD | Predicate disambiguation | batch_6a01309582e48190a05d47d96ffb7a46 |
completed | May 11, 2026, 1:27 a.m. |
Created at: April 28, 2026, 3:46 p.m.