Triple
T6703166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Maine (ACR-1) |
E152931
|
entity |
| Predicate | missionAtTimeOfSinking |
P72523
|
FINISHED |
| Object | show the flag and protect U.S. interests in Cuba |
—
|
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: show the flag and protect U.S. interests in Cuba | Statement: [USS Maine (ACR-1), missionAtTimeOfSinking, show the flag and protect U.S. interests in Cuba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionAtTimeOfSinking Context triple: [USS Maine (ACR-1), missionAtTimeOfSinking, show the flag and protect U.S. interests in Cuba]
-
A.
sankOnMaidenVoyage
Indicates that the subject vessel sank during its very first voyage.
-
B.
dateOfSinking
Indicates the specific calendar date on which an entity (typically a vessel or structure) sank.
-
C.
sunkDuring
Indicates that one entity was sunk in the course of, or as a result of, the event or time period represented by another entity.
-
D.
yearOfSinking
Indicates the specific calendar year in which an entity (typically a vessel or structure) sank.
-
E.
placeOfSinking
Indicates the location where an object or entity sank or was submerged.
- 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_69c68807adbc8190b8632df42b39eda0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d16897e48190b43eda2206b14d6a |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d089c7488190a00853fb12f53b2a |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1668a7c8190ae93951f9ba2df10 |
completed | March 27, 2026, 6:50 p.m. |
Created at: March 27, 2026, 2:06 p.m.