Triple
T26007094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thoroughbred-B |
E646788
|
entity |
| Predicate | typicalFSBSupport |
P158411
|
FINISHED |
| Object | 266 MHz |
—
|
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: 266 MHz | Statement: [Thoroughbred-B, typicalFSBSupport, 266 MHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFSBSupport Context triple: [Thoroughbred-B, typicalFSBSupport, 266 MHz]
-
A.
fsbSupportRange
chosen
Indicates that one entity supports or is compatible with a specified range of front-side bus (FSB) frequencies associated with another entity.
-
B.
IndependentSupportBase
Indicates that one entity serves as a foundational, self-sufficient support structure for another, not relying on additional supports or connections.
-
C.
providesSupportTo
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
-
D.
typeOfSupport
Indicates the kind or category of assistance, help, or backing provided in a given context.
-
E.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: April 22, 2026, 9:01 a.m.