Triple
T20080862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vijaya |
E499995
|
entity |
| Predicate | relativeObscurityIn |
P75548
|
FINISHED |
| Object | Mahabharata tradition |
—
|
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: Mahabharata tradition | Statement: [Vijaya, relativeObscurityIn, Mahabharata tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeObscurityIn Context triple: [Vijaya, relativeObscurityIn, Mahabharata tradition]
-
A.
relativeNotability
Indicates how notable or prominent one entity is in comparison to another entity or set of entities.
-
B.
popularityRelativeTo
Indicates how the popularity of one entity compares to the popularity of another entity, typically in terms of being more, less, or equally popular.
-
C.
hasRelativeProminenceComparedTo
Indicates that one entity has a greater, lesser, or otherwise specified level of prominence or importance when compared to another entity.
-
D.
isLesserKnown
chosen
Indicates that one entity is less widely recognized, famous, or familiar than another comparable entity.
-
E.
relativeLevel
Indicates a comparative relationship specifying how one entity’s level, degree, or intensity of some property stands relative to that of 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66557c19c8190b511857490bbd423 |
completed | April 20, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:41 p.m.