Triple

T36032775
Position Surface form Disambiguated ID Type / Status
Subject Findon E1042310 entity
Predicate publicTransportProvider P111896 FINISHED
Object Adelaide Metro 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: Adelaide Metro | Statement: [Findon, publicTransportProvider, Adelaide Metro]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: publicTransportProvider
Context triple: [Findon, publicTransportProvider, Adelaide Metro]
  • A. publicTransportOperatorFor chosen
    Indicates that one entity operates or manages public transportation services for another entity or area.
  • B. publicTransportNetworkType
    Indicates the type or category of public transportation network associated with or used by an entity.
  • C. publicTransportArea
    Indicates that a location or region is designated for or associated with public transportation services or facilities.
  • D. publicTransportation
    Indicates that an entity provides, uses, or is associated with shared, publicly accessible transportation services (such as buses, trains, or subways) rather than private transport.
  • E. publicTransportNode
    Indicates that a location functions as a node within a public transportation network, such as a stop, station, or interchange where services operate or connect.
  • 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_69f76e2d7e8c8190bac4e90734566799 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69ff956dc6548190979171d4b4068d47 completed May 9, 2026, 8:13 p.m.
PD Predicate disambiguation batch_69ff93dc39c481908a97a12c3ef7dfe7 completed May 9, 2026, 8:06 p.m.
Created at: May 3, 2026, 4:07 p.m.