Triple
T26930442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Station development |
E678199
|
entity |
| Predicate | landUseBeforeDevelopment |
P44099
|
FINISHED |
| Object | industrial land |
—
|
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: industrial land | Statement: [Central Station development, landUseBeforeDevelopment, industrial land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landUseBeforeDevelopment Context triple: [Central Station development, landUseBeforeDevelopment, industrial land]
-
A.
formerLandUse
chosen
Indicates the type of land use that characterized a location prior to its current or present use.
-
B.
previousBuildingUse
Indicates that a building previously served a specified use or function before its current one.
-
C.
landUseContext
Indicates the contextual setting or circumstances under which a particular piece of land is used or designated for a specific purpose.
-
D.
landUseChangeTo
Indicates a transition in how a piece of land is used, from its previous use to a new designated use.
-
E.
majorLandUse
Indicates the primary way a given area of land is utilized or designated (e.g., residential, commercial, agricultural).
- 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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62048ae408190b8be4222d537e3f3 |
completed | May 2, 2026, 4:03 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 6:12 a.m.