Triple
T23496584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolathunadu |
E571720
|
entity |
| Predicate | preColonialPolityOf |
P39667
|
FINISHED |
| Object | Kannur region |
—
|
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: Kannur region | Statement: [Kolathunadu, preColonialPolityOf, Kannur region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preColonialPolityOf Context triple: [Kolathunadu, preColonialPolityOf, Kannur region]
-
A.
precolonialPolity
chosen
Indicates that an entity functioned as a political or governing unit during the period before colonial rule was established in its region.
-
B.
preColonialOrigin
Indicates that something originated, was created, or first existed before the onset of the colonial period in a given region.
-
C.
preColonialStatus
Indicates the condition, role, or social-political standing an entity held prior to the onset of colonial rule.
-
D.
colonialPowerBefore
Indicates that one entity served as the colonial ruling power over another entity during an earlier, preceding time period.
-
E.
colonialPowerInHistory
Indicates that one entity historically exercised colonial control, dominance, or governance over another entity.
- 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7e00384819092729319a378d4ab |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:05 p.m.