Triple
T10133359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chestnut Grove plantation |
E226793
|
entity |
| Predicate | demolishedOrDestroyed |
P92154
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Chestnut Grove plantation, demolishedOrDestroyed, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demolishedOrDestroyed Context triple: [Chestnut Grove plantation, demolishedOrDestroyed, yes]
-
A.
demolishedWith
Indicates that one entity was destroyed or torn down using another specified tool, method, or agent.
-
B.
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.
-
C.
demolishedAfter
Indicates that one entity was demolished at a point in time later than the demolition of another entity.
-
D.
hasDemolitionOrDestruction
Indicates that one entity causes, undergoes, or is associated with the demolition or destruction of another entity.
-
E.
demolishedOrAbsorbed
Indicates that one entity has ceased to exist independently because it was either physically destroyed or organizationally absorbed into another entity.
- F. None of above. chosen
Provenance (4 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_69ca8433ec308190b8b25a6fe359c34c |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd33808048190b6023a6cd83fc179 |
completed | April 2, 2026, 2:23 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4fed19d481909d2c7ff1114664b6 |
completed | April 1, 2026, 5:03 p.m. |
Created at: March 30, 2026, 9:06 p.m.