Triple
T34459550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Arthur, comte de Lally |
E884594
|
entity |
| Predicate | yearOfAppointmentToIndiaCommand |
P178964
|
FINISHED |
| Object | 1756 |
—
|
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: 1756 | Statement: [Thomas Arthur, comte de Lally, yearOfAppointmentToIndiaCommand, 1756]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfAppointmentToIndiaCommand Context triple: [Thomas Arthur, comte de Lally, yearOfAppointmentToIndiaCommand, 1756]
-
A.
termStartAsGovernorGeneralOfIndia
Indicates the date or point in time when an individual began their tenure as Governor-General of India.
-
B.
arrivalYearInIndia
chosen
Indicates the year in which an entity arrived in India.
-
C.
termStartAsViceroyOfIndia
Indicates the date or point in time when an individual began serving in the role of Viceroy of India.
-
D.
enteredIndianService
Indicates that an individual began serving in the Indian government, military, or another official Indian institution.
-
E.
termEndAsGovernorGeneralOfIndia
Indicates the date or point in time when an individual’s tenure as Governor-General of India came to an end.
- 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_69f349c73a94819094dfcf50d00620b8 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: May 1, 2026, 2 a.m.