Triple
T17718160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bourtange |
E442259
|
entity |
| Predicate | disestablishedAsFortress |
P52894
|
FINISHED |
| Object | 1851 |
—
|
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: 1851 | Statement: [Bourtange, disestablishedAsFortress, 1851]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disestablishedAsFortress Context triple: [Bourtange, disestablishedAsFortress, 1851]
-
A.
fortressDemolishedIn
Indicates that a fortress was demolished or destroyed during a specified time or event.
-
B.
abandonedAsFort
chosen
Indicates that a location or structure previously used as a fort has been given up and is no longer maintained or occupied for defensive or military purposes.
-
C.
wasFortifiedBy
Indicates that a place or structure received defensive strengthening or fortification through the actions or resources of a specified agent or entity.
-
D.
opposedFortification
Indicates that one entity actively resisted, challenged, or worked against the strengthening or fortifying of another entity or location.
-
E.
fortressOriginallyBuiltBy
Indicates that a particular fortress was initially constructed by a specified builder or group.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e474834aec81909ab7e8224c5a39d7 |
completed | April 19, 2026, 6:21 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:06 a.m.