Triple
T2128247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revolutionary Armed Forces of Cuba |
E46473
|
entity |
| Predicate | hasReserveForces |
P35319
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Revolutionary Armed Forces of Cuba, hasReserveForces, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReserveForces Context triple: [Revolutionary Armed Forces of Cuba, hasReserveForces, yes]
-
A.
isStrategicReserveFor
Indicates that one entity is held or designated as a backup or contingency resource to be used strategically in support of another entity.
-
B.
commandedForcesOf
Indicates that one entity held command authority over the military or armed forces associated with another entity.
-
C.
garrisonedForce
Indicates that a military force is stationed in and occupies a specific location, typically for defense or control.
-
D.
besiegingForce
Indicates a military group that is surrounding and attacking a target location or force in an attempt to capture or subdue it.
-
E.
hasReserveTeam
Indicates that an organization, typically a sports club, maintains a secondary or backup team formally associated with its main team.
- 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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbb7659f48190871cb27faf47e18a |
completed | March 7, 2026, 5:45 a.m. |
| PD | Predicate disambiguation | batch_69abb7bd86cc8190938ef06c1ed6d969 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb895d11881908345032595a679ba |
completed | March 7, 2026, 5:33 a.m. |
Created at: March 4, 2026, 7:44 p.m.