Triple
T9928645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Ciudad Rodrigo (1812) |
E192585
|
entity |
| Predicate | breachLocation |
P87330
|
FINISHED |
| Object | greater breach near the northwest angle of the walls |
—
|
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: greater breach near the northwest angle of the walls | Statement: [Siege of Ciudad Rodrigo (1812), breachLocation, greater breach near the northwest angle of the walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breachLocation Context triple: [Siege of Ciudad Rodrigo (1812), breachLocation, greater breach near the northwest angle of the walls]
-
A.
locationOfBreachControl
Indicates the specific place or area where a breach is managed, contained, or controlled.
-
B.
leakLocation
Indicates the place or area where a leak occurs or is detected.
-
C.
breachedDuring
Indicates that one entity violated, broke, or failed to uphold another entity (such as a rule, contract, or security measure) within a specified time period or event.
-
D.
betrayalLocation
Indicates the place where an act of betrayal occurs or is carried out.
-
E.
notableLocationOfDamage
chosen
Indicates the specific place where damage is prominently present or has significantly occurred.
- 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb59d7ad08190982a1584547190bd |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:43 p.m.