Triple
T19350057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaunakiya Brāhmaṇa |
E483990
|
entity |
| Predicate | associatedWithRecension |
P62796
|
FINISHED |
| Object | Śaunaka recension of the Veda |
—
|
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: Śaunaka recension of the Veda | Statement: [Shaunakiya Brāhmaṇa, associatedWithRecension, Śaunaka recension of the Veda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRecension Context triple: [Shaunakiya Brāhmaṇa, associatedWithRecension, Śaunaka recension of the Veda]
-
A.
hasRecension
chosen
Indicates that one textual version or edition is a revised or alternative form of another text.
-
B.
associatedWithSee
Indicates a relationship where one entity is contextually or functionally linked to another through the act or concept of seeing or visual observation.
-
C.
associatedWithPub
Indicates that an entity has a connection or relationship with a particular publication (e.g., as source, reference, or related work).
-
D.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
E.
associatedWithRelease
Indicates a relationship where something is linked or connected to a particular release event, version, or distribution.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6190381c081909c747a22422fb02c |
completed | April 20, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:34 p.m.