Triple
T34085501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shravana Putrada Ekadashi |
E874165
|
entity |
| Predicate | legendOutcome |
P59870
|
FINISHED |
| Object | king blessed with a virtuous son |
—
|
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: king blessed with a virtuous son | Statement: [Shravana Putrada Ekadashi, legendOutcome, king blessed with a virtuous son]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legendOutcome Context triple: [Shravana Putrada Ekadashi, legendOutcome, king blessed with a virtuous son]
-
A.
legendStatus
Indicates that an entity holds, is assigned, or is associated with a particular legend-related status or classification.
-
B.
legend
Indicates that an entity is a traditional or historical story, figure, or narrative widely regarded as legendary rather than strictly factual.
-
C.
legendDetail
Indicates that additional explanatory or descriptive information is provided about a legend or key associated with another element.
-
D.
featuredLegend
Indicates that an entity is highlighted or showcased as a prominent or notable legend within a given context.
-
E.
outcomeOf
chosen
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
- 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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:52 a.m.