Triple
T16180748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honda Super Cub |
E392676
|
entity |
| Predicate | hasModel |
P2390
|
FINISHED |
| Object | C70 |
E392672
|
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: C70 | Statement: [Honda Super Cub, hasModel, C70]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: C70 Context triple: [Honda Super Cub, hasModel, C70]
-
A.
C70
chosen
C70 is a popular Honda Super Cub motorcycle variant known for its small-displacement four-stroke engine, step-through frame, and widespread use as an economical commuter bike.
-
B.
G70
G70 is a major Chinese national expressway connecting the southeastern city of Fuzhou with the northwestern city of Yinchuan.
-
C.
C-7
C-7 is a commuter rail line in the Cercanías Madrid network that connects central Madrid with various suburban areas.
-
D.
E70
E70 is a Nokia Eseries smartphone known for its fold-out full QWERTY keyboard and business-oriented features.
-
E.
E70
E70 is BMW's internal model designation for the second-generation X5 mid-size luxury SUV produced from 2006 to 2013.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2205c92b48190b7125dbbcff3662e |
completed | April 17, 2026, 11:58 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffff0022148190bc1810e76cf6d994 |
completed | May 10, 2026, 3:44 a.m. |
Created at: April 10, 2026, 5:02 a.m.