Triple
T16416362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 1108 |
E398694
|
entity |
| Predicate | supportsStopwatch |
P123344
|
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, supportsStopwatch, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsStopwatch Context triple: [Nokia 1108, supportsStopwatch, yes]
-
A.
supportsCountdown
Indicates that one entity enables or provides functionality for a countdown to be initiated, displayed, or managed for another entity.
-
B.
hasStopFeature
Indicates that one entity possesses or is equipped with a feature that enables stopping or halting an associated process, action, or movement.
-
C.
hasStop
Indicates that something (such as a route, service, or journey) includes or is associated with a particular stop or stopping point.
-
D.
supportsRewatch
Indicates that one entity allows or facilitates another entity being watched again after an initial viewing.
-
E.
supportEndedIn
Indicates that a previously existing support relationship between entities has come to an end at a specific point in time.
- 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_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. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:09 a.m.