Triple
T27697272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sundareswarar |
E698331
|
entity |
| Predicate | spouseFormOf |
P179016
|
FINISHED |
| Object | Parvati as Meenakshi |
—
|
NE NERFINISHED |
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: Parvati as Meenakshi | Statement: [Sundareswarar, spouseFormOf, Parvati as Meenakshi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseFormOf Context triple: [Sundareswarar, spouseFormOf, Parvati as Meenakshi]
-
A.
spouseType
Indicates the specific role or category of a person within a spousal relationship (e.g., husband, wife, partner).
-
B.
spouseFrom
Indicates that one person is the spouse of another person originating from a specified place or source.
-
C.
spouseMember
Indicates that one entity is the spouse (married partner) of another entity.
-
D.
spouse
Indicates that two entities are married to each other in a legally or socially recognized partnership.
-
E.
spouseInFamily
Indicates that a person is a spouse (married partner) within the context of a specific family unit.
- F. None of above. chosen
Provenance (4 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71995853c8190912025c0e83640c8 |
completed | May 3, 2026, 9:47 a.m. |
Created at: April 27, 2026, 2:55 p.m.