Triple
T36037038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kandyan–Portuguese War |
E1042431
|
entity |
| Predicate | aimOfPortuguese |
P64674
|
FINISHED |
| Object | annexation of Kingdom of Kandy |
—
|
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: annexation of Kingdom of Kandy | Statement: [Kandyan–Portuguese War, aimOfPortuguese, annexation of Kingdom of Kandy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimOfPortuguese Context triple: [Kandyan–Portuguese War, aimOfPortuguese, annexation of Kingdom of Kandy]
-
A.
aimOf
chosen
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
B.
roleInPortugal
Indicates that an entity holds or has held a specific role, position, or function within the context of Portugal.
-
C.
aliadoPrincipalDePortugal
Indicates that one entity serves as the primary ally of Portugal in a political, military, or strategic context.
-
D.
returnedToPortugal
Indicates that an entity went back to Portugal after having been away.
-
E.
grantedToPortugal
Indicates that a right, privilege, territory, or other benefit has been formally conferred or assigned to Portugal.
- 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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ad1bf27081909683fa99a367f556 |
completed | May 3, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.