Triple

T36843376
Position Surface form Disambiguated ID Type / Status
Subject Sapporo Municipal Subway 7000 series E910470 entity
Predicate usedOnTrackType P3832 FINISHED
Object rubber-tyred metro track 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: rubber-tyred metro track | Statement: [Sapporo Municipal Subway 7000 series, usedOnTrackType, rubber-tyred metro track]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedOnTrackType
Context triple: [Sapporo Municipal Subway 7000 series, usedOnTrackType, rubber-tyred metro track]
  • A. containsTrackType
    Indicates that one entity includes or is associated with a specific type or category of track.
  • B. usedTractionType
    Indicates the type of traction or drive mechanism that was employed in performing the action or operating the entity.
  • C. usesTrackage
    Indicates that one transportation operator or service runs its vehicles over railway or transit tracks that are owned or controlled by another entity.
  • D. composedTrackType
    Indicates that one entity is a track whose type or category is defined or characterized by another entity.
  • E. trackType chosen
    Indicates the specific kind or category of track associated with an entity, such as its functional or physical classification.
  • F. None of above.

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_69f76e7f65a881908651b702da592b6d completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f9fd6834cc8190aa27153d6a99f3bb completed May 5, 2026, 2:23 p.m.
PD Predicate disambiguation batch_69f7cf7890008190a8bc355ff2d61c86 completed May 3, 2026, 10:43 p.m.
Created at: May 3, 2026, 4:13 p.m.