Triple
T32955390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lawton Avenue |
E843084
|
entity |
| Predicate | hasWideningProject |
P179959
|
FINISHED |
| Object | Lawton Avenue Widening Project |
—
|
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: Lawton Avenue Widening Project | Statement: [Lawton Avenue, hasWideningProject, Lawton Avenue Widening Project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWideningProject Context triple: [Lawton Avenue, hasWideningProject, Lawton Avenue Widening Project]
-
A.
hasWideningProjects
chosen
Indicates that an entity is associated with projects aimed at expanding, enlarging, or increasing the capacity or scope of something.
-
B.
hasProjectIn
Indicates that an entity is involved with or associated with a project that takes place within a specified location or context.
-
C.
hasProject
Indicates that an entity is associated with or responsible for a particular project.
-
D.
hasSubproject
Indicates that a project includes another project as a subordinate or component part within its overall structure.
-
E.
hasUpgradeProject
Indicates that an entity is associated with a project whose purpose is to improve, enhance, or modernize that 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_69f3494a31f481909057136e49b4fe60 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: May 1, 2026, 1:21 a.m.