Triple
T26940565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carp Castle |
E678500
|
entity |
| Predicate | originalMainKeepDestroyedIn |
P58711
|
FINISHED |
| Object | 1945 |
—
|
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: 1945 | Statement: [Carp Castle, originalMainKeepDestroyedIn, 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalMainKeepDestroyedIn Context triple: [Carp Castle, originalMainKeepDestroyedIn, 1945]
-
A.
originalConstructionDestroyed
Indicates that the initially built or first version of an object, structure, or work has been destroyed or no longer exists in its original form.
-
B.
originalMansionDestroyedIn
chosen
Indicates that the original mansion was destroyed in the specified event, time, or circumstance.
-
C.
destroyedDuring
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
D.
mainStructurePartiallyDestroyedBy
Indicates that a primary structure has been damaged or destroyed to some extent as a result of the specified agent or event.
-
E.
possiblyDestroyedIn
Indicates that an entity may have been destroyed during or as a result of a specified event or situation.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: April 27, 2026, 6:18 a.m.