Triple
T24986474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assault on the Trocadero (1823) |
E625321
|
entity |
| Predicate | typeOfFortificationCaptured |
P102873
|
FINISHED |
| Object | coastal 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: coastal fortress | Statement: [Assault on the Trocadero (1823), typeOfFortificationCaptured, coastal fortress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfFortificationCaptured Context triple: [Assault on the Trocadero (1823), typeOfFortificationCaptured, coastal fortress]
-
A.
fortificationCaptured
Indicates that control of a defensive structure or fortified position has been taken from one party by another.
-
B.
fortificationTypeAssaulted
chosen
Indicates that an assault or attack was carried out against a specific type of fortification.
-
C.
fortificationTypeBesieged
Indicates that a specific type of fortification is the target of a siege or besieging action.
-
D.
wasFortifiedBy
Indicates that a place or structure received defensive strengthening or fortification through the actions or resources of a specified agent or entity.
-
E.
typeOfSiege
Indicates the specific kind or category of siege involved in a conflict or military operation.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 18, 2026, 6:03 a.m.