Triple
T17333169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oreshek Fortress |
E420864
|
entity |
| Predicate | recapturedIn |
P89143
|
FINISHED |
| Object | 1702 |
—
|
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: 1702 | Statement: [Oreshek Fortress, recapturedIn, 1702]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recapturedIn Context triple: [Oreshek Fortress, recapturedIn, 1702]
-
A.
recapturedUnder
Indicates that an entity was captured again while under a specific authority, condition, or legal framework.
-
B.
recapturedInConflict
chosen
Indicates that an entity was taken back or regained during a specific conflict or war after previously being lost or captured.
-
C.
recapturedWithSupportFrom
Indicates that an entity was taken back or regained with the assistance, backing, or involvement of another party or resource.
-
D.
wasRecapturedBy
Indicates that an entity which had previously escaped or been released was caught again by another entity.
-
E.
partiallyRecapturedBy
Indicates that an entity that was previously captured or controlled has been regained only in part by another entity, not fully restored to its prior captured state.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a0fa57881909071fd395b3d46c4 |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:43 a.m.