Triple

T97691
Position Surface form Disambiguated ID Type / Status
Subject IRT Division E1967 entity
Predicate hasFareControlIntegrationSince P3494 FINISHED
Object 1940 city takeover of IRT 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: 1940 city takeover of IRT | Statement: [IRT Division, hasFareControlIntegrationSince, 1940 city takeover of IRT]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFareControlIntegrationSince
Context triple: [IRT Division, hasFareControlIntegrationSince, 1940 city takeover of IRT]
  • A. hasFaregates
    Indicates that an entity is equipped with or contains faregates used to control or validate access, typically for paid entry.
  • B. fareSystem
    Indicates a relationship where a system is used to determine, collect, or manage fares or payments for transportation or similar services.
  • C. fareControl
    Indicates that an entity is responsible for monitoring, enforcing, or managing payment of fares for access to a service or facility.
  • D. hasFareZone
    Indicates that an entity is located within or associated with a specific fare zone used for pricing or ticketing.
  • E. hasPassengerTerminal
    Indicates that one entity possesses or is equipped with a passenger terminal used for boarding, alighting, or handling passengers.
  • 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_69a24d4862f881908cc8b89d3a78031d completed Feb. 28, 2026, 2:04 a.m.
NER Named-entity recognition batch_69a24feef1b08190bb9525f71cce053e completed Feb. 28, 2026, 2:16 a.m.
PD Predicate disambiguation batch_69a24ebe7b1c8190a6bfbf31dc7c7f07 completed Feb. 28, 2026, 2:11 a.m.
PDg Predicate description generation batch_69a24f4b4658819087902414959161fb completed Feb. 28, 2026, 2:13 a.m.
Created at: Feb. 28, 2026, 2:09 a.m.