Triple
T682439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Kandy |
E13210
|
entity |
| Predicate | maintainedIndependenceAgainst |
P243
|
FINISHED |
| Object | Portuguese colonial rule |
—
|
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: Portuguese colonial rule | Statement: [Kingdom of Kandy, maintainedIndependenceAgainst, Portuguese colonial rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainedIndependenceAgainst Context triple: [Kingdom of Kandy, maintainedIndependenceAgainst, Portuguese colonial rule]
-
A.
independenceFrom
chosen
Indicates that one entity is not controlled, governed, or significantly influenced by another entity.
-
B.
independenceRestored
Indicates that a previously dependent or controlled entity has regained its autonomy or self-governance.
-
C.
maintainedPeaceWith
Indicates that two entities sustained a state of peace or non-conflict with each other over a period of time.
-
D.
independenceRecognized
Indicates that one entity formally acknowledges another entity’s status as independent and self-governing.
-
E.
resultOfIndependence
Indicates that something exists or occurs as a consequence or outcome of an independence event or process.
- 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a06f9ee88190a2d757aacd8e3f5b |
completed | March 1, 2026, 8:24 p.m. |
| PD | Predicate disambiguation | batch_69a49d1f0ccc819088c1527beabcb718 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.