Triple
T16266417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moto3 |
E394886
|
entity |
| Predicate | tyreSupplier |
P30565
|
FINISHED |
| Object | Dunlop |
E392683
|
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: Dunlop | Statement: [Moto3, tyreSupplier, Dunlop]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dunlop Context triple: [Moto3, tyreSupplier, Dunlop]
-
A.
Dunlop
Dunlop is the middle name of A. D. Lindsay, a British academic and philosopher.
-
B.
Dunlop
chosen
Dunlop is a well-known tire manufacturer that produces high-performance motorcycle and automotive tires used in both professional racing and everyday driving.
-
C.
Dunlop
Dunlop is a residential suburb in the Belconnen district of Canberra, in the Australian Capital Territory.
-
D.
Goodyear
Goodyear is a rapidly growing suburban city in the Phoenix metropolitan area of Arizona, known for its master-planned communities, spring training baseball facilities, and proximity to desert recreation.
-
E.
Firestone
Firestone is a small town in Colorado’s Front Range region, known for its residential communities and proximity to the Denver metropolitan area.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c839788190b974d1d0d2525b88 |
completed | April 17, 2026, 2:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a001f8eac988190bdcba6778fbffd64 |
completed | May 10, 2026, 6:02 a.m. |
Created at: April 10, 2026, 5:05 a.m.