Triple
T16537473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 1110 |
E401727
|
entity |
| Predicate | hasCountdownTimer |
P54507
|
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 1110, hasCountdownTimer, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountdownTimer Context triple: [Nokia 1110, hasCountdownTimer, yes]
-
A.
hasTimer
Indicates that an entity is associated with or controlled by a timer mechanism that measures or limits a duration or interval.
-
B.
hasCountingPeriod
Indicates that there is a defined time span or interval over which occurrences, quantities, or measurements related to an entity are counted or aggregated.
-
C.
hasClock
Indicates that one entity possesses, contains, or is equipped with a clock.
-
D.
supportsCountdown
chosen
Indicates that one entity enables or provides functionality for a countdown to be initiated, displayed, or managed for another entity.
-
E.
hasCutoffTime
Indicates that there is a specific time limit or deadline by which an action, event, or process must be completed or initiated.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34559ca948190a9eb810b9b3be079 |
completed | April 18, 2026, 8:48 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.