Triple
T14382613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | siege of the citadel of Tournai |
E356639
|
entity |
| Predicate | fortificationTypeBesieged |
P113825
|
FINISHED |
| Object | bastioned citadel |
—
|
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: bastioned citadel | Statement: [siege of the citadel of Tournai, fortificationTypeBesieged, bastioned citadel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fortificationTypeBesieged Context triple: [siege of the citadel of Tournai, fortificationTypeBesieged, bastioned citadel]
-
A.
fortificationTypeAssaulted
Indicates that an assault or attack was carried out against a specific type of fortification.
-
B.
fortifiedBuilding
Indicates that a building is strengthened or reinforced for defense against attacks or intrusions.
-
C.
eraOfFortification
Indicates the historical time period during which a structure or site was fortified or equipped with defensive works.
-
D.
fortifiedSite
Indicates a site that has been strengthened or defended with protective structures or measures against attack.
-
E.
hasFortifications
Indicates that one entity possesses or is equipped with defensive structures or fortification works associated with it.
- F. None of above. chosen
Provenance (4 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de900d28c88190a37feee4743563de |
completed | April 14, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:16 a.m.