Triple
T18321044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 6300 |
E438878
|
entity |
| Predicate | javaSupport |
P58147
|
FINISHED |
| Object | MIDP 2.0 |
—
|
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: MIDP 2.0 | Statement: [Nokia 6300, javaSupport, MIDP 2.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: javaSupport Context triple: [Nokia 6300, javaSupport, MIDP 2.0]
-
A.
frameworkSupport
chosen
Indicates that one entity provides compatibility with, or operational support for, a particular framework used by another entity.
-
B.
developerSupport
Indicates that one entity provides technical assistance, resources, or guidance to help another entity develop, maintain, or improve software or related systems.
-
C.
theorySupports
Indicates that one theory provides justification, evidence, or logical backing for another claim, theory, or proposition.
-
D.
supportsCodeBuilder
Indicates that an entity provides compatibility with or functionality for a code-building tool or environment.
-
E.
languageTypeCovered
Indicates that one entity provides coverage, support, or applicability for a particular type or category of language associated with 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aa5a3508190a3025e71c11d79e2 |
completed | April 19, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.