Triple

T9668420
Position Surface form Disambiguated ID Type / Status
Subject Highland branch E233763 entity
Predicate usedForAfterConversion P98 FINISHED
Object light rail transit — 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: light rail transit | Statement: [Highland branch, usedForAfterConversion, light rail transit]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedForAfterConversion
Context triple: [Highland branch, usedForAfterConversion, light rail transit]
  • A. functionAfterConversion
    Indicates that one function or behavior occurs as a result of, or is valid only after, a specified conversion has taken place.
  • B. usedFor chosen
    Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
  • C. afterConversionKnownAs
    Indicates that an entity is referred to by a new name or identifier after undergoing a conversion or transformation.
  • D. convertedFor
    Indicates that one entity has been transformed, adapted, or reformatted specifically for use, compatibility, or suitability with another entity.
  • E. commandedByAfterConversion
    Indicates that an entity comes under the command or authority of another entity as a result of a conversion or transformation event.
  • 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_69ca848d3b6c8190ae98ea554dea58df completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9c3c06e4819080c1b8e66faa482f completed April 1, 2026, 10:29 p.m.
PD Predicate disambiguation batch_69ccd5b3239c8190b3ae3b9bd121e4bd completed April 1, 2026, 8:22 a.m.
Created at: March 30, 2026, 8:15 p.m.