Triple
T28608091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R3000 |
E724105
|
entity |
| Predicate | hasCoprocessorInterface |
P201180
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [R3000, hasCoprocessorInterface, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoprocessorInterface Context triple: [R3000, hasCoprocessorInterface, yes]
-
A.
hasInterface
Indicates that one entity provides, exposes, or is connected through a defined interface to another entity.
-
B.
hasSuperInterface
Indicates that one interface is declared to extend or inherit from another interface, making the latter a superinterface of the former.
-
C.
hasInterfaceElement
Indicates that one entity includes, exposes, or is associated with a specific interface element as part of its user interface or interaction surface.
-
D.
hasExpansionInterface
Indicates that an entity provides or supports an interface through which it can be expanded or extended with additional components or functionality.
-
E.
hasPrimaryInterface
Indicates that an entity is associated with its main or default interface used for interaction or communication.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69ffdd05d1908190957deb11392f4595 |
completed | May 10, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69ffdc0d33c881908b3483bee8a96540 |
completed | May 10, 2026, 1:14 a.m. |
| PDg | Predicate description generation | batch_69ffdd0486e08190a0f2ff4ce0aee13b |
completed | May 10, 2026, 1:19 a.m. |
Created at: April 28, 2026, 4:28 a.m.