Triple
T12020997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 5 series |
E286146
|
entity |
| Predicate | competesWith |
P1375
|
FINISHED |
| Object | Motorola Moto G series |
E72300
|
NE 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: Motorola Moto G series | Statement: [Nokia 5 series, competesWith, Motorola Moto G series]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Motorola Moto G series Context triple: [Nokia 5 series, competesWith, Motorola Moto G series]
-
A.
Moto G
chosen
Moto G is a popular line of budget-friendly Android smartphones known for offering strong performance and features at an affordable price.
-
B.
Moto E
Moto E is a line of budget-friendly Android smartphones produced by Motorola Mobility, known for offering essential features at low cost.
-
C.
Moto X
Moto X is a line of Android smartphones developed by Motorola Mobility, known for its near-stock software experience and emphasis on user customization and voice control features.
-
D.
Moto Z
Moto Z is a line of modular Android smartphones by Motorola known for its ultra-thin design and support for snap-on Moto Mods accessories.
-
E.
Moto One
Moto One is a line of Motorola smartphones known for offering a near-stock Android experience with timely software updates.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903ed15408190afc21afd57d6a737 |
completed | April 10, 2026, 2:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f48b62cad8819092beb72c604a4762 |
completed | May 1, 2026, 11:15 a.m. |
Created at: April 8, 2026, 9:47 p.m.