Triple
T18476610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vivasvan |
E451449
|
entity |
| Predicate | hasEpithetType |
P121211
|
FINISHED |
| Object | Vedic epithet of the sun |
—
|
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: Vedic epithet of the sun | Statement: [Vivasvan, hasEpithetType, Vedic epithet of the sun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEpithetType Context triple: [Vivasvan, hasEpithetType, Vedic epithet of the sun]
-
A.
hasEpithetOrigin
Indicates that the origin or source of an epithet (a descriptive name or label) is specified for an entity.
-
B.
epithetAppliedBy
Indicates that a particular epithet or descriptive label is used or assigned by a specific agent to a target entity.
-
C.
associatedWithEpithet
chosen
Indicates that an entity is linked to or described by a particular epithet or descriptive label.
-
D.
hasAppellationType
Indicates that an entity’s name or title is associated with a specific category or type of appellation.
-
E.
epithetOrTitle
Indicates that one entity serves as an epithet, honorific, or formal title used to designate or characterize another entity.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53063c0108190be71247567b5241b |
completed | April 19, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:35 a.m.