Triple
T27479941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kavichakravarti |
E693572
|
entity |
| Predicate | chakravartiMeaning |
P81241
|
FINISHED |
| Object | universal emperor |
—
|
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: universal emperor | Statement: [Kavichakravarti, chakravartiMeaning, universal emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chakravartiMeaning Context triple: [Kavichakravarti, chakravartiMeaning, universal emperor]
-
A.
ParthaMeans
Indicates that one entity serves as the meaning, definition, or semantic interpretation of another entity.
-
B.
hasMeaningInSanskrit
chosen
Indicates that one entity (such as a word, phrase, or symbol) possesses a specific meaning when interpreted in the Sanskrit language.
-
C.
VajranabhaIs
Indicates that something or someone is identified as or characterized by being Vajranabha.
-
D.
becamePracharakOf
Indicates that one entity assumed the role or position of a pracharak (propagator/missionary worker) associated with another entity, such as an organization or movement.
-
E.
chantMeaning
Indicates that an entity performs or conveys the meaning or content of a chant in relation to another entity or context.
- 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_69ef5381f2648190a2392d0fab833095 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62e470e1c819099cbecb791f35990 |
completed | May 2, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:59 p.m.