Triple
T23040886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glasgow, Delaware |
E573730
|
entity |
| Predicate | zonedPrimarilyFor |
P56223
|
FINISHED |
| Object | residential use |
—
|
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: residential use | Statement: [Glasgow, Delaware, zonedPrimarilyFor, residential use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zonedPrimarilyFor Context triple: [Glasgow, Delaware, zonedPrimarilyFor, residential use]
-
A.
zonedUse
Indicates the designated or permitted type of land use assigned to a property or area under zoning regulations.
-
B.
zonedTo
Indicates that one entity is assigned or designated to fall within the jurisdiction, service area, or regulatory zone of another entity.
-
C.
isPrimarilyUsedAs
Indicates that one entity serves mainly or most commonly in the role, function, or purpose specified by the other entity.
-
D.
regionPrimaryUse
Indicates the main functional purpose or dominant activity for which a region is used.
-
E.
primarilyFor
chosen
Indicates that something is mainly intended, designed, or used for a particular purpose, function, or beneficiary, even if it may have secondary uses.
- 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18513fc54819096d761a0be75b774 |
completed | April 29, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:53 p.m.