Triple
T16416359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 1108 |
E398694
|
entity |
| Predicate | supportsAlarmClock |
P106326
|
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: [Nokia 1108, supportsAlarmClock, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAlarmClock Context triple: [Nokia 1108, supportsAlarmClock, yes]
-
A.
supportsAlarm
chosen
Indicates that one entity is capable of handling, enabling, or being compatible with an alarm feature or functionality for another entity.
-
B.
hasEmergencyAlarm
Indicates that an entity is equipped with or associated with an emergency alarm system that can be activated in urgent situations.
-
C.
hasClock
Indicates that one entity possesses, contains, or is equipped with a clock.
-
D.
supportsEmergencySOS
Indicates that one entity provides or is compatible with an emergency SOS function or service for another entity.
-
E.
alarmSignal
Indicates that an alarm or warning signal is being emitted, triggered, or active in response to some condition or event.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32877ff248190886717d3329421a7 |
completed | April 18, 2026, 6:45 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.