Triple
T9092514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vithalbhai Patel |
E217923
|
entity |
| Predicate | hasCitizenshipDuring |
P31432
|
FINISHED |
| Object | British rule in India |
—
|
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: British rule in India | Statement: [Vithalbhai Patel, hasCitizenshipDuring, British rule in India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCitizenshipDuring Context triple: [Vithalbhai Patel, hasCitizenshipDuring, British rule in India]
-
A.
citizenshipDuringLifetime
chosen
Indicates that an entity held citizenship in a particular country or political unit at some point during its lifetime.
-
B.
hasTypicalCitizenship
Indicates that an entity is generally or commonly a citizen of a specified country or jurisdiction.
-
C.
citizenshipGrantedYear
Indicates the specific year in which an entity was officially granted citizenship.
-
D.
hasHostCitizenship
Indicates that an entity holds citizenship in, or is a citizen of, a specified host country or jurisdiction.
-
E.
requiresCitizenship
Indicates that one entity can only obtain, access, or participate in another entity if it holds citizenship of a specified country or jurisdiction.
- 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_69ca83d8ab5881909d8fddae363b32b1 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc96b18b24819097b525ddad3a85c0 |
completed | April 1, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:14 p.m.