Triple
T11489490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yanam district |
E272366
|
entity |
| Predicate | deJureTransferToIndiaOn |
P57141
|
FINISHED |
| Object | 1962 |
—
|
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: 1962 | Statement: [Yanam district, deJureTransferToIndiaOn, 1962]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deJureTransferToIndiaOn Context triple: [Yanam district, deJureTransferToIndiaOn, 1962]
-
A.
jurisdictionTransferred
Indicates that legal authority or control over a matter, case, or entity has been moved from one jurisdiction to another.
-
B.
deJureTransferDate
chosen
Indicates the official legal date on which ownership or rights are formally transferred from one party to another.
-
C.
fullSovereigntyTransferred
Indicates that complete and exclusive governing authority has been formally transferred from one entity to another.
-
D.
portedTo
Indicates that something has been adapted or transferred from its original environment or platform to run or function on a different one.
-
E.
transferAgreement
Indicates a formal arrangement in which ownership, rights, or responsibilities are transferred from one party to another.
- 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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85a20df608190992543b4d7006f8a |
completed | April 10, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69d808736c5c8190899b5b3b2e797f65 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.