Triple
T14498002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia N92 |
E359553
|
entity |
| Predicate | supportsMemoryCardExpansion |
P17632
|
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 N92, supportsMemoryCardExpansion, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMemoryCardExpansion Context triple: [Nokia N92, supportsMemoryCardExpansion, yes]
-
A.
supportsMemoryCard
chosen
Indicates that one entity is compatible with and can accept or use a memory card associated with another entity.
-
B.
expandableRAM
Indicates that a device’s RAM can be increased beyond its original capacity, typically by adding or upgrading memory modules.
-
C.
ramExpandableTo
Indicates that a device’s RAM can be increased from its current capacity up to a specified maximum amount.
-
D.
hasExternalMemory
Indicates that an entity is associated with or utilizes memory resources located outside its own primary or internal storage.
-
E.
expansionSlots
Indicates that an entity provides one or more hardware expansion slots available for adding additional 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9311cc748190880c784f173b7f2b |
completed | April 14, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:21 a.m.