Triple
T31044670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Przemyśl Fortress |
E791089
|
entity |
| Predicate | laterRecapturedBy |
P34167
|
FINISHED |
| Object | Central Powers |
—
|
NE NERFINISHED |
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: Central Powers | Statement: [Przemyśl Fortress, laterRecapturedBy, Central Powers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRecapturedBy Context triple: [Przemyśl Fortress, laterRecapturedBy, Central Powers]
-
A.
wasRecapturedBy
chosen
Indicates that an entity which had previously escaped or been released was caught again by another entity.
-
B.
placeOfRecapture
Indicates the location where an entity that had escaped or been released was subsequently captured again.
-
C.
recapturedInConflict
Indicates that an entity was taken back or regained during a specific conflict or war after previously being lost or captured.
-
D.
recapturedUnder
Indicates that an entity was captured again while under a specific authority, condition, or legal framework.
-
E.
recapturedWithSupportFrom
Indicates that an entity was taken back or regained with the assistance, backing, or involvement of another party or resource.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff1e3e13c08190bb8990c44716b746 |
completed | May 9, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_69ff1dfcaf2c8190aaf2b428d57b7782 |
completed | May 9, 2026, 11:43 a.m. |
Created at: April 29, 2026, 8:59 p.m.