Triple
T19732320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vishrava |
E473885
|
entity |
| Predicate | ethnicOrMythicGroup |
P137130
|
FINISHED |
| Object | Brahmin sage |
—
|
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: Brahmin sage | Statement: [Vishrava, ethnicOrMythicGroup, Brahmin sage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicOrMythicGroup Context triple: [Vishrava, ethnicOrMythicGroup, Brahmin sage]
-
A.
ethnicGroupInMythologyOf
Indicates that a particular ethnic group appears within, is featured by, or is thematically represented in the mythology or mythological traditions of another culture or group.
-
B.
typeOfMythologicalGroup
Indicates that one entity is classified as a specific kind or category of mythological group to which the other entity belongs.
-
C.
ethnicGroupNamed
Indicates that an ethnic group bears or is identified by a particular name.
-
D.
ancestralGroup
Indicates that one entity is a broader ancestral lineage, population, or group from which the other entity descends or originates.
-
E.
ethnicGroupBase
Indicates that one entity serves as the primary or foundational ethnic group from which another entity is derived, associated, or defined.
- F. None of above. chosen
Provenance (4 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e651596b98819090bcaf05c7b74555 |
completed | April 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:47 p.m.