Triple
T28737407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moody Centre Station |
E730838
|
entity |
| Predicate | partOfExtensionProject |
P9951
|
FINISHED |
| Object | Evergreen Extension |
—
|
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: Evergreen Extension | Statement: [Moody Centre Station, partOfExtensionProject, Evergreen Extension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfExtensionProject Context triple: [Moody Centre Station, partOfExtensionProject, Evergreen Extension]
-
A.
hasExtensionProject
Indicates that an entity is associated with or participates in a specific extension project.
-
B.
definesExtension
Indicates that one entity specifies or establishes the extension, scope, or detailed form of another entity.
-
C.
openedAsPartOfProject
chosen
Indicates that something was opened or initiated as a component or phase of a specific project.
-
D.
formerExtension
Indicates that one entity previously served as an extension or subsidiary part of another entity, but no longer holds that status.
-
E.
hasExtensionInto
Indicates that one entity stretches, projects, or continues into the space, area, or domain of another entity.
- 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: April 28, 2026, 6:01 a.m.