Triple
T15571449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia N79 |
E374250
|
entity |
| Predicate | hasChangeableXpressOnCovers |
P105880
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nokia N79, hasChangeableXpressOnCovers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChangeableXpressOnCovers Context triple: [Nokia N79, hasChangeableXpressOnCovers, true]
-
A.
hasExpressTracks
Indicates that a transportation route or facility includes tracks designated for express service, allowing faster travel with fewer stops than regular tracks.
-
B.
hasCoverType
Indicates that one entity possesses or is associated with a specific type or category of cover.
-
C.
supportsCustomCovers
chosen
Indicates that one entity provides the capability for another entity to use or define custom cover designs or images.
-
D.
hasCoverFeature
Indicates that one entity serves as a prominent or featured element on the cover of another entity (such as a publication, product, or media item).
-
E.
canExpress
Indicates that an entity has the ability or capacity to convey, articulate, or communicate something (such as an idea, emotion, or property).
- 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e2025888190a2b6240296bba13e |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:10 a.m.