Triple
T24882544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglo-Dutch Treaty of 1814 |
E622750
|
entity |
| Predicate | confirmedBritishRuleOver |
P6044
|
FINISHED |
| Object | Ceylon |
—
|
NE NERFINISHED |
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: Ceylon | Statement: [Anglo-Dutch Treaty of 1814, confirmedBritishRuleOver, Ceylon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confirmedBritishRuleOver Context triple: [Anglo-Dutch Treaty of 1814, confirmedBritishRuleOver, Ceylon]
-
A.
capitalDuringBritishRule
Indicates that a place served as the capital of a region or polity specifically during the period of British rule.
-
B.
viewOnBritishRule
Indicates a person or group's attitude, opinion, or stance toward British colonial rule.
-
C.
maintainedColonialRuleOver
Indicates that one entity continued to exercise colonial control, governance, or dominance over another entity for a period of time.
-
D.
broughtUnderBritishCrown
chosen
Indicates that an entity was placed under the authority, control, or sovereignty of the British Crown.
-
E.
administrativeStatusUnderBritish
Indicates the type or condition of an entity’s administrative relationship or governance status under British authority.
- 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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:24 a.m.