Triple
T4229800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pepe San Román |
E94550
|
entity |
| Predicate | invasionOutcome |
P44060
|
FINISHED |
| Object | Bay of Pigs invasion failed |
—
|
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: Bay of Pigs invasion failed | Statement: [Pepe San Román, invasionOutcome, Bay of Pigs invasion failed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invasionOutcome Context triple: [Pepe San Román, invasionOutcome, Bay of Pigs invasion failed]
-
A.
wasInvadedBy
Indicates that a place or territory was subjected to an incursion or attack carried out by another entity or group.
-
B.
conqueredIn
Indicates that one entity gained control over another entity or territory as a result of a specific conquest event or campaign.
-
C.
plannedInvasionOf
Indicates that one entity has formulated or organized an invasion targeting another entity.
-
D.
invasionDate
Indicates the date on which an invasion event occurred or began.
-
E.
partOfConflictOutcome
chosen
Indicates that one entity represents a specific component or aspect of the overall outcome of a conflict involving another entity.
- 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_69b3453700a08190ae88792e3dc63207 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e61ccc081909b880baf1d6a0f24 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f3bd188190b0cd613e8a5c1683 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.