Triple
T6537033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lawrence Avenue East |
E168189
|
entity |
| Predicate | hasLandUseAlongCorridor |
P37665
|
FINISHED |
| Object | commercial |
—
|
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: commercial | Statement: [Lawrence Avenue East, hasLandUseAlongCorridor, commercial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandUseAlongCorridor Context triple: [Lawrence Avenue East, hasLandUseAlongCorridor, commercial]
-
A.
hasLandUseCharacter
Indicates that one entity possesses or is associated with a particular type or pattern of land use.
-
B.
landUseIncludes
chosen
Indicates that a specified land area contains or permits the specified type(s) of land use within its boundaries.
-
C.
hasNearbyLandUse
Indicates that one land area is located close to another area characterized by a specific type of land use.
-
D.
belongsToUrbanCorridor
Indicates that something is part of, contained within, or functionally integrated into a continuous urban corridor or urbanized area.
-
E.
hasNearbyDevelopmentCorridor
Indicates that an entity is located close to, or directly influenced by, a designated development corridor such as a planned or existing zone of concentrated growth or infrastructure.
- 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_69c68a51564081909e93aee0dbd9cca3 |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6ce07332481909a5a7964282eb776 |
completed | March 27, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69c6acf3e3708190b052ec774e607cb7 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:49 p.m.