Triple
T16996038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitsubishi Fuso Truck and Bus Corporation |
E412317
|
entity |
| Predicate | sharesBrandNameWith |
P48444
|
FINISHED |
| Object | Fuso |
E412317
|
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: Fuso | Statement: [Mitsubishi Fuso Truck and Bus Corporation, sharesBrandNameWith, Fuso]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fuso Context triple: [Mitsubishi Fuso Truck and Bus Corporation, sharesBrandNameWith, Fuso]
-
A.
Fuso
chosen
Fuso is a commercial vehicle manufacturer best known for its trucks and buses, operating as part of Daimler’s global automotive group.
-
B.
Tōyō
Tōyō is the given name of Sesshū Tōyō, a renowned Japanese Zen Buddhist monk and master of ink painting during the Muromachi period.
-
C.
Nippani
Nippani is a town in the northern part of Karnataka, India, known for its agriculture, small-scale industries, and location near the Maharashtra border.
-
D.
Fuseta
Fuseta is a small coastal fishing village in Portugal’s Algarve region, known for its sandy island beaches, traditional seafood, and relaxed atmosphere.
-
E.
Mibuchi
Mibuchi is a Japanese surname borne by individuals such as Tadahiko Mibuchi.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d2879af081909665f9f838bcfbe7 |
completed | April 18, 2026, 6:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a011b433e688190ac8dda10638a197f |
completed | May 10, 2026, 11:56 p.m. |
Created at: April 10, 2026, 5:32 a.m.