Triple

T13061220
Position Surface form Disambiguated ID Type / Status
Subject Okayama–Hakata section E329199 entity
Predicate railwayCharacter P108254 FINISHED
Object mostly elevated and tunnel LITERAL 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: mostly elevated and tunnel | Statement: [Okayama–Hakata section, railwayCharacter, mostly elevated and tunnel]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: railwayCharacter
Context triple: [Okayama–Hakata section, railwayCharacter, mostly elevated and tunnel]
  • A. railwayClass
    Indicates the specific classification or category assigned to a railway or railway service within a defined system.
  • B. railcode
    Indicates that an entity is associated with a specific railway code used for identification or classification within a rail system.
  • C. railroadClass
    Indicates the classification or category of a railroad according to an established system (e.g., by size, revenue, or regulatory status).
  • D. railComponent
    Indicates a relationship where one entity is a structural or functional part of a rail or railway system component of another entity.
  • E. typicalLocomotiveClass
    Indicates that one locomotive class is the standard or most commonly used class for a given context, operator, or service.
  • 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_69d80771749c81909a6d9197b9504872 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d980e7ee548190b4b18bdb1357c359 completed April 10, 2026, 10:59 p.m.
PD Predicate disambiguation batch_69d9803d46688190bac6b7d208f08d01 completed April 10, 2026, 10:57 p.m.
PDg Predicate description generation batch_69d980e622e8819087a69bfb1660dd64 completed April 10, 2026, 10:59 p.m.
Created at: April 9, 2026, 8:59 p.m.