Triple
T5243365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sri Bhashya |
E118398
|
entity |
| Predicate | upholdsConcept |
P9935
|
FINISHED |
| Object | Brahman with attributes |
—
|
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: Brahman with attributes | Statement: [Sri Bhashya, upholdsConcept, Brahman with attributes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upholdsConcept Context triple: [Sri Bhashya, upholdsConcept, Brahman with attributes]
-
A.
defendsConcept
Indicates that one entity actively supports and argues in favor of a particular concept, idea, or theory, often in response to criticism or challenge.
-
B.
moralConcept
Indicates that one entity represents or embodies a moral or ethical concept in relation to another.
-
C.
supportsPrinciple
chosen
Indicates that one entity endorses, upholds, or actively backs a particular principle or doctrine.
-
D.
establishesPrinciple
Indicates that an entity formulates, defines, or sets forth a foundational rule, guideline, or standard that others are expected to follow or build upon.
-
E.
holdsUnder
Indicates that one entity maintains possession, control, or validity of another entity subject to certain conditions, constraints, or a specific 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b4da7308190856cdcee9cca41eb |
completed | March 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69bd77c1397c8190a7fd844d7a396e54 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:49 p.m.