Triple
T19976015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashopton |
E493691
|
entity |
| Predicate | buildingsDemolished |
P29327
|
FINISHED |
| Object | all main village buildings |
—
|
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: all main village buildings | Statement: [Ashopton, buildingsDemolished, all main village buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingsDemolished Context triple: [Ashopton, buildingsDemolished, all main village buildings]
-
A.
demolishedOrDestroyed
Indicates that one entity has caused another entity to be torn down, ruined, or rendered unusable, typically through deliberate demolition or destructive force.
-
B.
demolishedWith
Indicates that one entity was destroyed or torn down using another specified tool, method, or agent.
-
C.
demolishedOriginalStructures
chosen
Indicates that one entity has completely destroyed or removed the original structures associated with another entity.
-
D.
previousBuildingDemolished
Indicates that a building which previously occupied the same site or fulfilled the same role has been demolished.
-
E.
demolishedAfter
Indicates that one entity was demolished at a point in time later than the demolition of another entity.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d0f4fb48190ad63afeff3513523 |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:26 p.m.