Triple
T12556735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 3100 |
E295235
|
entity |
| Predicate | talkTime |
P103409
|
FINISHED |
| Object | up to 6 hours (approximate) |
—
|
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 6 hours (approximate) | Statement: [Nokia 3100, talkTime, up to 6 hours (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: talkTime Context triple: [Nokia 3100, talkTime, up to 6 hours (approximate)]
-
A.
telecommunicationsProvider
Indicates that one entity provides telecommunications services (such as phone, internet, or data connectivity) to another entity.
-
B.
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).
-
C.
hasAirtime
Indicates that an entity possesses or is allocated a certain amount of airtime (e.g., broadcast time or mobile call credit).
-
D.
carrierOf
Indicates that one entity serves as the medium, vehicle, or host that contains, transports, or conveys another entity.
-
E.
wirelessOperator
Indicates that an entity operates, manages, or provides services for a wireless communication system or network for 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_69d6ad9cac2c81908e8a7bed82d1e21d |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d95410d0b0819097646edd1b837104 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 11:47 p.m.