Triple
T29181837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motorola Q9c |
E739763
|
entity |
| Predicate | hasSideKeys |
P139605
|
FINISHED |
| Object | volume control |
—
|
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: volume control | Statement: [Motorola Q9c, hasSideKeys, volume control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSideKeys Context triple: [Motorola Q9c, hasSideKeys, volume control]
-
A.
hasExtraKeys
chosen
Indicates that an entity possesses additional keys beyond the primary or expected set of keys associated with another entity or resource.
-
B.
hasKeyDua
Indicates that one entity possesses or is associated with a specific secondary or backup key related to another entity.
-
C.
hasSideChain
Indicates that one entity possesses a secondary chain or branching group attached to its main structure.
-
D.
hasKeyRelationship
Indicates a relationship where one entity serves as a key (e.g., identifier, access token, or primary reference) that grants access to, controls, or uniquely identifies another entity.
-
E.
supportsMultipleKeys
Indicates that an entity is capable of handling, accepting, or operating with more than one key simultaneously or in parallel.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 28, 2026, 11:57 a.m.