Triple
T16610071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mehta |
E403542
|
entity |
| Predicate | isUsedAsTitleHistorically |
P9146
|
FINISHED |
| Object | revenue official |
—
|
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: revenue official | Statement: [Mehta, isUsedAsTitleHistorically, revenue official]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedAsTitleHistorically Context triple: [Mehta, isUsedAsTitleHistorically, revenue official]
-
A.
usedAsTitleUntil
Indicates that a particular title was held or used by an entity up to (and including or until) a specified end time.
-
B.
isHistoricTitle
Indicates that a given title or designation was used in the past and is no longer current, but is retained for historical reference.
-
C.
usedAsTitleBeforeName
chosen
Indicates that a term or phrase functions as a formal title placed immediately before a person's name.
-
D.
usedAsTitleInFull
Indicates that something functions as a formal title within the complete, official version of a name or designation.
-
E.
firstUseAsTitleBy
Indicates that an entity is the first to use a given term, phrase, or designation as a formal title for 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3609572508190a5d7e6c3e0a8cf95 |
completed | April 18, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.