Triple
T1122446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cornelius Vanderbilt II House |
E24640
|
entity |
| Predicate | demolishedFor |
P17656
|
FINISHED |
| Object | commercial development |
—
|
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 development | Statement: [Cornelius Vanderbilt II House, demolishedFor, commercial development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demolishedFor Context triple: [Cornelius Vanderbilt II House, demolishedFor, commercial development]
-
A.
demolished
Indicates that one entity completely destroyed or razed another entity, typically a structure or object, so that it no longer exists in its previous form.
-
B.
demolishedToMakeWayFor
chosen
Indicates that one entity was intentionally destroyed or removed in order to create space for another entity or development.
-
C.
reasonForDemolition
Indicates the cause, justification, or circumstance that led to a structure or object being demolished.
-
D.
demolitionEnd
Indicates the point in time or event at which a demolition process is completed or comes to an end.
-
E.
demolitionAnnounced
Indicates that an official announcement has been made that a demolition of something is planned or will take place.
- 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_69a4940712c88190aa244f3fc6070a65 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4749ac8190b0fbddac2e9b2586 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.