Triple
T17240681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 6310 |
E418488
|
entity |
| Predicate | talkTimeMax |
P103409
|
FINISHED |
| Object | up to 7 hours |
—
|
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: up to 7 hours | Statement: [Nokia 6310, talkTimeMax, up to 7 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: talkTimeMax Context triple: [Nokia 6310, talkTimeMax, up to 7 hours]
-
A.
supportsTalkTime
chosen
Indicates that an entity provides or enables a specified duration of talk time for another entity (e.g., a device, plan, or service).
-
B.
cellularOptions
Indicates that one entity specifies or provides available cellular network or mobile connectivity options for another entity.
-
C.
hasAirtime
Indicates that an entity possesses or is allocated a certain amount of airtime (e.g., broadcast time or mobile call credit).
-
D.
telecommunicationsProvider
Indicates that one entity provides telecommunications services (such as phone, internet, or data connectivity) to another entity.
-
E.
telecomCircle
Indicates the regional telecommunications service area or jurisdiction within which a telecom provider operates or a phone number is registered.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e1f385c8190ae44e702923b6f66 |
completed | April 19, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.