Triple
T735355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Playa Girón |
E14918
|
entity |
| Predicate | hasRoleInEvent |
P4073
|
FINISHED |
| Object | main landing site of Bay of Pigs invasion |
—
|
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: main landing site of Bay of Pigs invasion | Statement: [Playa Girón, hasRoleInEvent, main landing site of Bay of Pigs invasion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleInEvent Context triple: [Playa Girón, hasRoleInEvent, main landing site of Bay of Pigs invasion]
-
A.
hasRole
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
B.
eventRole
chosen
Indicates the specific function, capacity, or part an entity plays within an event or occurrence.
-
C.
participatedInEvent
Indicates that an entity took part in or was actively involved in a specific event.
-
D.
isInvited
Indicates that one entity has extended an invitation to another entity to participate in or attend something.
-
E.
hasGlobalRole
Indicates that an entity holds a role or permission set that applies across an entire system or domain, rather than being limited to a specific scope or context.
- 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_69a4934d9930819099eed80096b0597d |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a66820548190b373deb117187c2c |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4fafee081909bf356854c09aaff |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.