Triple
T28726407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Badajoz |
E730235
|
entity |
| Predicate | hasBreaches |
P173386
|
FINISHED |
| Object | Trinidad breach |
—
|
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: Trinidad breach | Statement: [Siege of Badajoz, hasBreaches, Trinidad breach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBreaches Context triple: [Siege of Badajoz, hasBreaches, Trinidad breach]
-
A.
compromisedOn
Indicates that two or more parties reached a mutual agreement by each conceding or adjusting their original positions.
-
B.
riskIfBreached
Indicates that a breach of the referenced entity or condition would expose or create a potential risk or harm.
-
C.
associatedWithCompromise
Indicates a relationship where an entity is linked to, involved in, or affected by a security compromise or breach.
-
D.
afterBreached
Indicates that one event or state occurs subsequent to another event or state having been breached or violated.
-
E.
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.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 28, 2026, 5:56 a.m.