Triple
T26410750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Château de Coucy |
E663951
|
entity |
| Predicate | demolishedPartiallyIn |
P114779
|
FINISHED |
| Object | 1917 |
—
|
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: 1917 | Statement: [Château de Coucy, demolishedPartiallyIn, 1917]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demolishedPartiallyIn Context triple: [Château de Coucy, demolishedPartiallyIn, 1917]
-
A.
demolishedAsPartOf
Indicates that one entity was demolished as a component or consequence of a larger demolition event or project involving another entity.
-
B.
demolishedPortions
chosen
Indicates that certain parts or sections of an object, structure, or entity have been destroyed or torn down.
-
C.
partiallyDestroyed
Indicates that an entity has been damaged or ruined to a significant extent but not completely destroyed.
-
D.
demolishedWith
Indicates that one entity was destroyed or torn down using another specified tool, method, or agent.
-
E.
demolishedOrDestroyed
Indicates that one entity has caused another entity to be torn down, ruined, or rendered unusable, typically through deliberate demolition or destructive force.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6113143f481909c64dfc1975e3a59 |
completed | May 2, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 11:37 p.m.