Triple
T6524988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NI roboRIO |
E151279
|
entity |
| Predicate | hasNonVolatileStorage |
P35145
|
FINISHED |
| Object | onboard flash memory |
—
|
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: onboard flash memory | Statement: [NI roboRIO, hasNonVolatileStorage, onboard flash memory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNonVolatileStorage Context triple: [NI roboRIO, hasNonVolatileStorage, onboard flash memory]
-
A.
nonVolatile
chosen
Indicates that the associated entity or state does not change, disappear, or lose its value when power is removed or over time.
-
B.
isMajorStorageFor
Indicates that one entity serves as the primary or main storage location or repository for another entity.
-
C.
hasInternalHardDrive
Indicates that one entity possesses an internal hard drive as a built-in storage component.
-
D.
hasPhysicalMedium
Indicates that one entity serves as the tangible carrier or material form through which another entity exists, is stored, or is transmitted.
-
E.
hasBackupBattery
Indicates that an entity is equipped with an additional battery intended to provide power when the primary power source is unavailable or fails.
- 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_69c687f522748190b3058405553cdabd |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ad9831f88190a2b64cf6bc8c9a11 |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:45 p.m.