Triple
T36669707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motorola C115 |
E905377
|
entity |
| Predicate | hasMonoblockDesign |
P200037
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Motorola C115, hasMonoblockDesign, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonoblockDesign Context triple: [Motorola C115, hasMonoblockDesign, true]
-
A.
hasDesignSide
Indicates that one entity is located on, associated with, or corresponds to a particular side or face of another entity’s design.
-
B.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
-
C.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
D.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
E.
hasDesignOption
Indicates that an entity is associated with or offers a particular design alternative or configurable design choice.
- F. None of above. chosen
Provenance (4 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_69f76e6f10008190aea41746aa1b186e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff6c061c6c81909ff485e9cafc88a2 |
completed | May 9, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ff6aaf886c8190a3c87d089453f3de |
completed | May 9, 2026, 5:11 p.m. |
| PDg | Predicate description generation | batch_69ff6c04fa208190b1fab40a71ef923f |
completed | May 9, 2026, 5:16 p.m. |
Created at: May 3, 2026, 4:12 p.m.