Triple
T37743753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Up-country Tamils |
E940790
|
entity |
| Predicate | repatriationAgreements |
P138561
|
FINISHED |
| Object | Sirima–Shastri Pact |
—
|
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: Sirima–Shastri Pact | Statement: [Up-country Tamils, repatriationAgreements, Sirima–Shastri Pact]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repatriationAgreements Context triple: [Up-country Tamils, repatriationAgreements, Sirima–Shastri Pact]
-
A.
repatriationStatus
Indicates the current state or progress of returning a person or asset back to their country or original place of origin.
-
B.
repatriatedBy
Indicates that an entity is brought or returned back to its country or place of origin by a specified agent or authority.
-
C.
repatriatedOn
Indicates that something or someone was returned to their country or place of origin on a specific date or time.
-
D.
repatriationCountryTo
Indicates the country to which someone or something is returned or sent back, typically to their place of origin or citizenship.
-
E.
resultOfTreaties
chosen
Indicates that something exists, occurs, or holds true as a consequence or outcome of one or more treaties.
- 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_69f76ee0e32c8190b40a3b4cf590337c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:19 p.m.