Triple
T12021039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 3310 (2017) |
E286147
|
entity |
| Predicate | talkTimeClaimed |
P5171
|
FINISHED |
| Object | up to 22 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 22 hours | Statement: [Nokia 3310 (2017), talkTimeClaimed, up to 22 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: talkTimeClaimed Context triple: [Nokia 3310 (2017), talkTimeClaimed, up to 22 hours]
-
A.
hasAirtime
Indicates that an entity possesses or is allocated a certain amount of airtime (e.g., broadcast time or mobile call credit).
-
B.
marketingClaim
chosen
Indicates that an entity asserts or promotes a statement about a product, service, or offering for marketing or advertising purposes.
-
C.
usedToClaim
Indicates that something is employed as evidence, justification, or support in making a particular claim.
-
D.
mainClaim
Indicates that one statement is presented as the central or primary assertion being made about a topic.
-
E.
telecommunicationsProvider
Indicates that one entity provides telecommunications services (such as phone, internet, or data connectivity) to another entity.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902b6ebbc8190b13c44a61c6f81b9 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.