Triple
T20277267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Mantua (1796–1797) |
E503047
|
entity |
| Predicate | garrisonStatus |
P17805
|
FINISHED |
| Object | Austrian-held fortress |
—
|
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: Austrian-held fortress | Statement: [Siege of Mantua (1796–1797), garrisonStatus, Austrian-held fortress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonStatus Context triple: [Siege of Mantua (1796–1797), garrisonStatus, Austrian-held fortress]
-
A.
garrisonState
chosen
Indicates that a military force is stationed in or assigned to defend a particular state or territory.
-
B.
garrisonSize
Indicates the number of troops or defenders stationed at a particular location as its garrison.
-
C.
garrisonFunction
Indicates that an entity serves as a military garrison or base for another entity, providing housing, support, or operational facilities for its forces.
-
D.
garrisonMaintainedBy
Indicates that a military garrison is operated, supported, or kept in readiness by a specified controlling entity.
-
E.
garrisonLabel
Indicates the designation or identifying label assigned to a military garrison associated with an entity.
- 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_69e0b4b0e79c8190bd61f22ef1329fa8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e675e4cdfc81908c7cb4519a7d744b |
completed | April 20, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 10:35 a.m.