Triple
T20658757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheridan Expressway |
E507698
|
entity |
| Predicate | purposeOfConversion |
P45854
|
FINISHED |
| Object | improve neighborhood connectivity |
—
|
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: improve neighborhood connectivity | Statement: [Sheridan Expressway, purposeOfConversion, improve neighborhood connectivity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfConversion Context triple: [Sheridan Expressway, purposeOfConversion, improve neighborhood connectivity]
-
A.
reasonForConversion
chosen
Indicates the cause, motivation, or justification behind a particular conversion event or change.
-
B.
operationalPurpose
Indicates the function, role, or intended use that an entity is designed or configured to perform in an operational context.
-
C.
placeOfConversion
Indicates the location where an entity undergoes a religious, ideological, or formal conversion.
-
D.
involvesConversionTo
Indicates that one entity undergoes a change of form, type, or state resulting in another entity.
-
E.
purposeOfGrant
Indicates that a grant is provided with the specific purpose, objective, or intended use described by the associated entity or activity.
- 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b2eefd5c8190a71d4be690a6ae0e |
completed | April 20, 2026, 11:12 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:43 a.m.