Triple
T26783087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paramabhattaraka |
E670301
|
entity |
| Predicate | meaningOfRootBhattaraka |
P77856
|
FINISHED |
| Object | lord |
—
|
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: lord | Statement: [Paramabhattaraka, meaningOfRootBhattaraka, lord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningOfRootBhattaraka Context triple: [Paramabhattaraka, meaningOfRootBhattaraka, lord]
-
A.
ParthaMeans
chosen
Indicates that one entity serves as the meaning, definition, or semantic interpretation of another entity.
-
B.
hasMeaningInSanskrit
Indicates that one entity (such as a word, phrase, or symbol) possesses a specific meaning when interpreted in the Sanskrit language.
-
C.
fatehMeaning
Indicates that one entity conveys or expresses the meaning, interpretation, or semantic content of another.
-
D.
relationshipWithBharata
Indicates that there exists a specific type of relationship or association between an entity and Bharata.
-
E.
regardsBrahmaAs
Indicates that one entity considers, views, or treats another entity as Brahma (the supreme or creator deity).
- 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 4:10 a.m.