Triple
T11025429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rishabhanatha |
E260604
|
entity |
| Predicate | birthCityTradition |
P60104
|
FINISHED |
| Object | Ikshvaku dynasty capital |
—
|
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: Ikshvaku dynasty capital | Statement: [Rishabhanatha, birthCityTradition, Ikshvaku dynasty capital]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birthCityTradition Context triple: [Rishabhanatha, birthCityTradition, Ikshvaku dynasty capital]
-
A.
traditionalInCity
Indicates that something is customary, long-established, or historically rooted within a particular city.
-
B.
containsTraditionalCity
Indicates that one entity geographically or administratively includes or encompasses a traditional city within its boundaries.
-
C.
traditionAt
chosen
Indicates that a particular tradition is practiced, observed, or associated at a specific place or location.
-
D.
traditionInheritedFrom
Indicates that a tradition has been passed down or derived from an earlier source, group, or culture.
-
E.
culturalTradition
Indicates a relationship where certain practices, beliefs, or customs are recognized as part of a shared cultural heritage passed down within a group or society.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797bf78a48190a37b423812827d4e |
completed | April 9, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69d7440087ac8190aef2e6f6b13b2635 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:25 p.m.