Triple
T15343860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Antwerp |
E366865
|
entity |
| Predicate | fortificationFeature |
P22477
|
FINISHED |
| Object | outer ring of forts |
—
|
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: outer ring of forts | Statement: [Siege of Antwerp, fortificationFeature, outer ring of forts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fortificationFeature Context triple: [Siege of Antwerp, fortificationFeature, outer ring of forts]
-
A.
fortifiedSite
Indicates a site that has been strengthened or defended with protective structures or measures against attack.
-
B.
hasFortifications
chosen
Indicates that one entity possesses or is equipped with defensive structures or fortification works associated with it.
-
C.
isFortificationGatewayOf
Indicates that a gateway or entrance structure serves as an access point or defensive portal belonging to a specific fortification.
-
D.
fortifiedBuilding
Indicates that a building is strengthened or reinforced for defense against attacks or intrusions.
-
E.
fortificationCommanded
Indicates that one entity holds authority over and directs the defense or operation of a particular fortification or fortified structure.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e163a3c8190ab933411372c1573 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.