Triple
T33327575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Catarina |
E853306
|
entity |
| Predicate | seizureContext |
P176494
|
FINISHED |
| Object | Dutch–Portuguese colonial rivalry in Asia |
—
|
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–Portuguese colonial rivalry in Asia | Statement: [Santa Catarina, seizureContext, Dutch–Portuguese colonial rivalry in Asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seizureContext Context triple: [Santa Catarina, seizureContext, Dutch–Portuguese colonial rivalry in Asia]
-
A.
locationOfSeizure
Indicates the place or setting where a seizure event occurs.
-
B.
seizureCompleted
Indicates that a previously initiated seizure (e.g., of property, assets, or items) has been fully carried out and brought to completion.
-
C.
methodOfSeizure
Indicates the manner or technique by which something is taken, captured, or seized.
-
D.
dateOfSeizure
Indicates the specific date on which a seizure (such as confiscation or legal taking of property) occurred.
-
E.
hasTypicalSeizureType
Indicates that an entity is associated with or characterized by a particular usual or predominant type of seizure.
- 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_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. |
| PDg | Predicate description generation | batch_69f6e312d7fc819094dec41810f2585d |
completed | May 3, 2026, 5:54 a.m. |
Created at: May 1, 2026, 1:33 a.m.