Triple
T33327590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Catarina |
E853306
|
entity |
| Predicate | seizedByShip |
P23911
|
FINISHED |
| Object | Dutch East India Company warships |
—
|
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: Dutch East India Company warships | Statement: [Santa Catarina, seizedByShip, Dutch East India Company warships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seizedByShip Context triple: [Santa Catarina, seizedByShip, Dutch East India Company warships]
-
A.
capturedShip
chosen
Indicates that one party has taken control of another party's ship, typically by force or seizure.
-
B.
confiscatedBy
Indicates that something has been taken away and seized by an authority or agent, typically as a legal or disciplinary action.
-
C.
capturedShipType
Indicates that one entity has taken possession of another entity’s ship, specifying the type or category of the ship that was captured.
-
D.
shipSankIn
Indicates that a specific ship sank (was lost or submerged) in a particular location or body of water.
-
E.
seizedCapital
Indicates that one entity forcibly took control of another entity’s capital city.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:33 a.m.