Triple
T19272402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saptarishi era |
E481960
|
entity |
| Predicate | traditionallyTransmittedBy |
P20591
|
FINISHED |
| Object | Hindu scholars |
—
|
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: Hindu scholars | Statement: [Saptarishi era, traditionallyTransmittedBy, Hindu scholars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyTransmittedBy Context triple: [Saptarishi era, traditionallyTransmittedBy, Hindu scholars]
-
A.
traditionInheritedFrom
chosen
Indicates that a tradition has been passed down or derived from an earlier source, group, or culture.
-
B.
compiledByTradition
Indicates that something has been assembled, organized, or codified according to established customs, practices, or traditional authority rather than by a single identifiable author.
-
C.
traditionSince
Indicates that a tradition has been continuously practiced or recognized starting from a specified point in time.
-
D.
mainTradition
Indicates that one entity represents the primary or dominant tradition associated with another entity.
-
E.
traditionallyOneOf
Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbb9bd5881909d86c5def7770fdd |
completed | April 20, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:29 p.m.