Triple
T28819955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Ciudad Rodrigo |
E727734
|
entity |
| Predicate | breachesMade |
P90431
|
FINISHED |
| Object | two main breaches in 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: two main breaches in the walls | Statement: [Siege of Ciudad Rodrigo, breachesMade, two main breaches in the walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breachesMade Context triple: [Siege of Ciudad Rodrigo, breachesMade, two main breaches in the walls]
-
A.
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.
-
B.
breaksOver
Indicates that one entity moves or crashes forcefully onto the surface or boundary of another entity, typically dispersing or shattering upon contact.
-
C.
rupturesDuring
Indicates that one event or process ruptures or breaks while another specified event or time period is occurring.
-
D.
hasTransgression
Indicates that one entity has committed, is responsible for, or is associated with a violation, offense, or wrongdoing in relation to another entity or rule.
-
E.
defensiveLineBreached
chosen
Indicates that a defensive line or barrier has been successfully penetrated or overcome by an opposing force.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658f653948190978153d28f5e772c |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:34 a.m.