Triple
T26904776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Central America |
E677221
|
entity |
| Predicate | estimatedGoldCargoValueAtTime |
P124858
|
FINISHED |
| Object | about US$1.6 million |
—
|
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: about US$1.6 million | Statement: [SS Central America, estimatedGoldCargoValueAtTime, about US$1.6 million]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedGoldCargoValueAtTime Context triple: [SS Central America, estimatedGoldCargoValueAtTime, about US$1.6 million]
-
A.
approximateValueStolenInUSDAtTheTime
Indicates the estimated amount of money, in U.S. dollars and valued at the time of the theft, that was stolen in the described incident.
-
B.
monetaryValue
Indicates the amount of money associated with an entity, event, or transaction.
-
C.
amountInvolvedApprox
chosen
Indicates that the relationship specifies an approximate value or quantity involved in an action, event, or transaction.
-
D.
valueRelativeToGuilder
Indicates that something’s value is expressed in terms of, or compared relative to, the guilder currency.
-
E.
treasureInvolved
Indicates that a situation, event, or action involves or is related to treasure in some significant way.
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 5:58 a.m.