Triple
T36669711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motorola C115 |
E905377
|
entity |
| Predicate | hasBacklitDisplay |
P33708
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Motorola C115, hasBacklitDisplay, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBacklitDisplay Context triple: [Motorola C115, hasBacklitDisplay, true]
-
A.
hasBacklitKeyboard
Indicates that an entity is equipped with a keyboard that includes built-in lighting behind the keys.
-
B.
usesBacklightTechnology
chosen
Indicates that one entity employs backlight technology to illuminate or enhance the visibility of another entity or its display.
-
C.
hasLumen
Indicates that one entity possesses or is characterized by a specific luminous intensity or light output measured in lumens.
-
D.
displayBrightnessTypical
Indicates the typical or standard brightness level at which something (such as a display) is normally operated or presented.
-
E.
hasAlwaysOnDisplay
Indicates that an entity features an always-on display capability that remains visible without fully waking the device.
- 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_69f76e6f10008190aea41746aa1b186e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: May 3, 2026, 4:12 p.m.