Triple

T22421757
Position Surface form Disambiguated ID Type / Status
Subject Mitsubishi Fuso Truck and Bus Corporation E554264 entity
Predicate brand P1500 FINISHED
Object Fuso NE NERFINISHED

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, brand, Fuso]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fuso
Context triple: [Mitsubishi Fuso Truck and Bus Corporation, brand, 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 (2 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_69e11e4f2d0c819091aa3558ea2ee630 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f1594b08d88190bb61a30397d0ffa5 completed April 29, 2026, 1:05 a.m.
Created at: April 16, 2026, 8:46 p.m.