Triple
T32993878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maharawal |
E844166
|
entity |
| Predicate | titleUsageStatus |
P29608
|
FINISHED |
| Object | largely ceremonial in modern 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: largely ceremonial in modern India | Statement: [Maharawal, titleUsageStatus, largely ceremonial in modern India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleUsageStatus Context triple: [Maharawal, titleUsageStatus, largely ceremonial in modern India]
-
A.
titleUsage
chosen
Indicates how a title is applied, referenced, or used in relation to an entity or context.
-
B.
titleStatus
Indicates the current legal or administrative state of a title (such as ownership, validity, or processing stage) in relation to an entity or record.
-
C.
titleUsedSince
Indicates that a particular title has been in use starting from a specified point in time.
-
D.
nameUsageStatus
Indicates the current status or condition of how a name is being used or applied in a given context.
-
E.
usageStatus
Indicates the current state or condition of how something is being used, such as whether it is active, inactive, available, or in use.
- 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_69f3494d99988190b502c68926af2c4d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fee25dbca481909e6f1c255122b3a8 |
completed | May 9, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69fee1c8915c8190b08b63e42881f1a9 |
completed | May 9, 2026, 7:27 a.m. |
Created at: May 1, 2026, 1:22 a.m.