Triple

T33447380
Position Surface form Disambiguated ID Type / Status
Subject Scarborough Subway Extension of Line 2 Bloor–Danforth E856542 entity
Predicate cityCouncilApproval P38661 FINISHED
Object approved by Toronto City Council 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: approved by Toronto City Council | Statement: [Scarborough Subway Extension of Line 2 Bloor–Danforth, cityCouncilApproval, approved by Toronto City Council]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: cityCouncilApproval
Context triple: [Scarborough Subway Extension of Line 2 Bloor–Danforth, cityCouncilApproval, approved by Toronto City Council]
  • A. cityCouncilApproved chosen
    Indicates that a city council has formally reviewed and granted approval for a proposed action, decision, or measure.
  • B. hasCityCouncil
    Indicates that an entity is governed or administered by a specific city council.
  • C. councilCan
    Indicates that a council has the authority or permission to perform a specified action or exercise a particular power.
  • D. council
    Indicates that an entity serves as a governing or advisory council for another entity or within a particular domain.
  • E. councilOutcome
    Indicates the result or decision produced by a council after its deliberation or proceedings.
  • 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_69f34971b75881908be360bb041f003c completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6e4a8c5c88190a304f849fcb5e7a5 completed May 3, 2026, 6:01 a.m.
PD Predicate disambiguation batch_69f6e3da41948190a4cfe866ce184f73 completed May 3, 2026, 5:57 a.m.
Created at: May 1, 2026, 1:37 a.m.