Triple
T6054384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TI-85 |
E134872
|
entity |
| Predicate | backupBatteryType |
P59438
|
FINISHED |
| Object | CR1616 or CR1620 |
—
|
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: CR1616 or CR1620 | Statement: [TI-85, backupBatteryType, CR1616 or CR1620]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backupBatteryType Context triple: [TI-85, backupBatteryType, CR1616 or CR1620]
-
A.
secondaryBatteryType
chosen
Indicates the type or category of a secondary (backup or auxiliary) battery associated with an entity.
-
B.
batteryType
Indicates the specific kind or category of battery associated with or used by an entity.
-
C.
hasBackupBattery
Indicates that an entity is equipped with an additional battery intended to provide power when the primary power source is unavailable or fails.
-
D.
secondaryBattery
Indicates that an entity has a secondary battery system or backup power source in addition to its primary battery.
-
E.
hasInternalBattery
Indicates that one entity possesses a built-in power source contained within itself, rather than relying solely on external power.
- 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_69c00877b6d4819096b0e163728b73a3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05708fda48190ad3d1860969ebb6a |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049edc6f0819092ca620d9073ad26 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:09 p.m.