Triple

T18665075
Position Surface form Disambiguated ID Type / Status
Subject Halifax urban road network E456303 entity
Predicate hasMajorArterial P107273 FINISHED
Object Sackville Drive
Sackville Drive is a key arterial roadway serving as a major commercial and traffic corridor in the Halifax Regional Municipality of Nova Scotia, Canada.
E1957182 NE 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: Sackville Drive | Statement: [Halifax urban road network, hasMajorArterial, Sackville Drive]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Sackville Drive
Triple: [Halifax urban road network, hasMajorArterial, Sackville Drive]
Generated description
Sackville Drive is a key arterial roadway serving as a major commercial and traffic corridor in the Halifax Regional Municipality of Nova Scotia, Canada.

Provenance (5 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_69d8d38f72b4819090a935175d9ca8af completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5508e02788190bdea6099f08db4f0 completed April 19, 2026, 10 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2a1e014f008190a6f84a9ddd32eca7 completed June 11, 2026, 2:31 a.m.
NEDg Description generation batch_6a2a2823d8408190b62a5e80e6878daf completed June 11, 2026, 3:14 a.m.
NED2 Entity disambiguation (via description) batch_6a2a288b41bc8190bfdc652f18191347 completed June 11, 2026, 3:16 a.m.
Created at: April 10, 2026, 11:48 a.m.