Triple
T28639736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varma |
E724887
|
entity |
| Predicate | isUsedAsTitle |
P81381
|
FINISHED |
| Object | royal title in some South Indian dynasties |
—
|
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: royal title in some South Indian dynasties | Statement: [Varma, isUsedAsTitle, royal title in some South Indian dynasties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedAsTitle Context triple: [Varma, isUsedAsTitle, royal title in some South Indian dynasties]
-
A.
usedAsTitleInFull
Indicates that something functions as a formal title within the complete, official version of a name or designation.
-
B.
usesTitleIn
Indicates that an entity is referred to using a particular title within a specified context or medium.
-
C.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
-
D.
usedAsTitleElement
chosen
Indicates that one entity functions as a title-forming component or element within another entity’s title.
-
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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 4:43 a.m.