Triple
T12467281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 8146 |
E297956
|
entity |
| Predicate | hasEnhancedFeaturesComparedToBasicModels |
P28765
|
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 8146, hasEnhancedFeaturesComparedToBasicModels, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnhancedFeaturesComparedToBasicModels Context triple: [Nokia 8146, hasEnhancedFeaturesComparedToBasicModels, yes]
-
A.
hasMoreAdvanced
Indicates that one entity possesses a higher level of advancement, development, or sophistication compared to another entity.
-
B.
featureLevelComparedTo
chosen
Indicates a comparative relationship between entities based on their feature level, specifying how one entity’s feature level ranks relative to another’s.
-
C.
lessFeatureRichThan
Indicates that one entity has fewer or less advanced features or capabilities than another entity.
-
D.
enhancedBy
Indicates that one entity’s value, effectiveness, or impact is increased or improved as a result of another entity.
-
E.
featuresModel
Indicates that one entity includes, exposes, or is characterized by a particular model as one of its defining components or capabilities.
- 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_69d6ada270808190b1a2b2e7b02bb426 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e626dbc8190ac7dcdb542ba9b0c |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d3f701c81909dd0e00251ac8553 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.