Triple
T13097269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 3120 |
E310622
|
entity |
| Predicate | hasExternalMemoryCardSlot |
P17632
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Nokia 3120, hasExternalMemoryCardSlot, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExternalMemoryCardSlot Context triple: [Nokia 3120, hasExternalMemoryCardSlot, no]
-
A.
hasExternalMemory
Indicates that an entity is associated with or utilizes memory resources located outside its own primary or internal storage.
-
B.
supportsMemoryCard
chosen
Indicates that one entity is compatible with and can accept or use a memory card associated with another entity.
-
C.
hasDedicatedCameraButton
Indicates that an object or device includes a specific physical button intended solely for activating or controlling the camera function.
-
D.
requiresCartridgeSlotOf
Indicates that one entity needs to use or be connected to the cartridge slot provided by another entity in order to function or be compatible.
-
E.
hasMemoryIn
Indicates that an entity possesses or stores memory, information, or experiences within a specified context, location, or medium.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9814e88a0819088418c792ce7aa57 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:04 p.m.