Triple

T26070849
Position Surface form Disambiguated ID Type / Status
Subject Tokyo Metro Ginza Line at Tameike-sanno E657539 entity
Predicate isOnHistoricLine P159916 FINISHED
Object Tokyo Metro Ginza Line 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: Tokyo Metro Ginza Line | Statement: [Tokyo Metro Ginza Line at Tameike-sanno, isOnHistoricLine, Tokyo Metro Ginza Line]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isOnHistoricLine
Context triple: [Tokyo Metro Ginza Line at Tameike-sanno, isOnHistoricLine, Tokyo Metro Ginza Line]
  • A. isInHistoricRegion
    Indicates that an entity is located within or belongs to a historically recognized geographic region.
  • B. isInHistoricRegister
    Indicates that an entity has been officially listed or recorded in a recognized historic register or registry.
  • C. isHistoric
    Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
  • D. isHistoricCrossing
    Indicates that a crossing between two locations has historical significance, such as being notable in history, heritage, or past events.
  • E. isHistoricCourseAt
    Indicates that a course has historically been offered or held at a particular institution or location.
  • F. None of above. chosen

Provenance (4 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_69ee5bbe539081909efc7f9dd7c1b53c completed April 26, 2026, 6:38 p.m.
NER Named-entity recognition batch_69f606ca69b08190977693fd1f8e8ae4 completed May 2, 2026, 2:14 p.m.
PD Predicate disambiguation batch_69f5aff889988190ad10bcf1a280f717 completed May 2, 2026, 8:04 a.m.
PDg Predicate description generation batch_69f5f6b32a8881909baa0db57b80d56a completed May 2, 2026, 1:05 p.m.
Created at: April 26, 2026, 7:28 p.m.