Triple

T7715015
Position Surface form Disambiguated ID Type / Status
Subject Tokyo Gaikan Expressway E174857 entity
Predicate hasAbbreviation P43 FINISHED
Object C3 E685070 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: C3 | Statement: [Tokyo Gaikan Expressway, hasAbbreviation, C3]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: C3
Context triple: [Tokyo Gaikan Expressway, hasAbbreviation, C3]
  • A. C3 chosen
    C3 is the route designation for the Tokyo Gaikan Expressway, a major orbital expressway forming part of the ring road system around Tokyo, Japan.
  • B. C3F
    C3F is the official abbreviation for the United States Navy's Third Fleet, a major operational fleet responsible for naval forces in the eastern and northern Pacific Ocean.
  • C. C2
    C2 is the software consultancy founded by Ward Cunningham, best known for creating the first wiki and contributing to agile software development practices.
  • D. C-3a
    C-3a is a commuter rail line within the Cercanías Madrid network serving suburban areas around Spain’s capital.
  • E. C4
    C4 is a military acronym referring to the integrated system of command, control, communications, and computers that supports decision-making and operations.
  • 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_69c6995c463c8190a14458036249d419 completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c702cbe74081908502ac670515fa3c completed March 27, 2026, 10:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8be2831788190a8ba7340b5d4d439 completed March 29, 2026, 5:52 a.m.
Created at: March 27, 2026, 4:04 p.m.