Triple
T17980651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Padmavati |
E449591
|
entity |
| Predicate | relationshipToLakshmi |
P60881
|
FINISHED |
| Object | regional manifestation of Lakshmi |
—
|
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: regional manifestation of Lakshmi | Statement: [Padmavati, relationshipToLakshmi, regional manifestation of Lakshmi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToLakshmi Context triple: [Padmavati, relationshipToLakshmi, regional manifestation of Lakshmi]
-
A.
relationshipToDeities
chosen
Indicates how an entity is connected or related to one or more deities, such as through worship, lineage, role, or status.
-
B.
relatedNameOfGod
Indicates that one entity is a name, title, or designation that refers to or is associated with God.
-
C.
relationshipToTopa
Indicates a familial or social relationship that an entity has specifically with Topa.
-
D.
roleOfReferencedDeity
Indicates that one entity specifies the function, status, or position held by a deity that is referenced in relation to another entity or context.
-
E.
associatedWithTirthankara
Indicates a relationship where an entity has a connection, link, or relevance to a Tirthankara.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b202aab88190b44851808c75a848 |
completed | April 19, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.