Triple
T32955395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lawton Avenue |
E843084
|
entity |
| Predicate | wideningProjectStatus |
P171656
|
FINISHED |
| Object | partially completed |
—
|
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: partially completed | Statement: [Lawton Avenue, wideningProjectStatus, partially completed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wideningProjectStatus Context triple: [Lawton Avenue, wideningProjectStatus, partially completed]
-
A.
expansionProject
Indicates a project whose primary purpose is to enlarge, extend, or increase the capacity, scope, or reach of something.
-
B.
statusOfOriginalProject
Indicates the current state or condition of the original project in relation to its lifecycle or progress.
-
C.
projectState
chosen
Indicates the current status or phase that a project is in within its lifecycle.
-
D.
stateProject
Indicates that a project is initiated, funded, or directly administered by a governmental state authority.
-
E.
expansionStatus
Indicates the current state or phase of growth, enlargement, or extension of something relative to its previous or intended size or scope.
- 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_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:21 a.m.