Triple
T17014969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valley Line West |
E412797
|
entity |
| Predicate | projectScope |
P22281
|
FINISHED |
| Object | west-end LRT extension |
—
|
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: west-end LRT extension | Statement: [Valley Line West, projectScope, west-end LRT extension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectScope Context triple: [Valley Line West, projectScope, west-end LRT extension]
-
A.
projectArea
Indicates the geographic or spatial extent covered or affected by a given project.
-
B.
projectModel
Indicates a relationship where one entity serves as a model, template, or representation for a project or projected outcome involving another entity.
-
C.
workScope
chosen
Indicates the defined range, extent, and boundaries of tasks or responsibilities involved in a particular work activity or project.
-
D.
productionScope
Indicates the extent or boundaries of what is included in a given production activity or process.
-
E.
project
Indicates that an entity plans, organizes, or carries out a structured effort or initiative aimed at achieving a specific goal or outcome.
- 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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d47f198c8190b0473f638101f606 |
completed | April 18, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.