Triple
T31633219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Bellegarde (1793) |
E807225
|
entity |
| Predicate | fortificationTypeInvolved |
P172092
|
FINISHED |
| Object | mountain 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: mountain fortress | Statement: [Siege of Bellegarde (1793), fortificationTypeInvolved, mountain fortress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fortificationTypeInvolved Context triple: [Siege of Bellegarde (1793), fortificationTypeInvolved, mountain fortress]
-
A.
involvesFortificationType
chosen
Indicates that the relationship or action includes or is associated with a specific type of fortification (e.g., defensive structure or fortified feature).
-
B.
fortificationTypeAssaulted
Indicates that an assault or attack was carried out against a specific type of fortification.
-
C.
fortificationTypeDefended
Indicates the specific type of fortification that an entity is responsible for defending or protecting.
-
D.
fortificationBuilt
Indicates that a fortification was constructed or established, linking the structure to the event or agent responsible for its building.
-
E.
wasFortifiedBy
Indicates that a place or structure received defensive strengthening or fortification through the actions or resources of a specified agent or 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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:46 p.m.