Triple

T20814620
Position Surface form Disambiguated ID Type / Status
Subject JR-P17 E512403 entity
Predicate ticketingICCardBrand P69490 FINISHED
Object manaca 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: manaca | Statement: [JR-P17, ticketingICCardBrand, manaca]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: manaca
Context triple: [JR-P17, ticketingICCardBrand, manaca]
  • A. manaca
    manaca is a rechargeable contactless smart card used for public transportation and electronic payments in the Nagoya area of Japan.
  • B. Manaca chosen
    Manaca is a rechargeable contactless smart card used for public transportation and electronic payments in the Nagoya metropolitan area of Japan.
  • C. МАН
    МАН is the abbreviation for the Mongolian People's Party, one of Mongolia's major political parties and the country’s oldest modern political organization.
  • D. manisero
    A manisero is a resident or native of Manises, a municipality in the province of Valencia, Spain.
  • E. MaNa
    MaNa is a professional StarCraft II player known for competing at the highest levels of international esports tournaments.
  • 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_69e0b4cd25088190b48ca9700cd24efc completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c2d4e43c8190aecce82a3f7e2de0 completed April 21, 2026, 12:20 a.m.
Created at: April 16, 2026, 12:41 p.m.