Triple
T1544299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yonkers Raceway |
E32940
|
entity |
| Predicate | zoningClassification |
P9954
|
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: [Yonkers Raceway, zoningClassification, commercial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoningClassification Context triple: [Yonkers Raceway, zoningClassification, commercial]
-
A.
zoningCharacter
Indicates how the regulatory or functional nature of a geographic area is defined or classified in terms of land-use zoning.
-
B.
cityPlanningDesignation
chosen
Indicates how an area is officially classified or designated within urban or municipal planning (e.g., residential, commercial, industrial).
-
C.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
D.
territorialDesignation
Indicates that an entity is assigned, defined, or recognized in terms of a specific geographic or territorial area.
-
E.
mapDesignation
Indicates a formal label or identifier that is assigned to something specifically for use on a map.
- 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_69a885ed29088190a3c2d5a3d100c16e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa95c1a2948190a2b98469afec1a7d |
completed | March 6, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69a907b2453c8190a41f6b88c8217d1e |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.