Triple
T38660680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nanda |
E940324
|
entity |
| Predicate | spouseBeforeOrdination |
P198410
|
FINISHED |
| Object | Janapadakalyāṇī |
—
|
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: Janapadakalyāṇī | Statement: [Nanda, spouseBeforeOrdination, Janapadakalyāṇī]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseBeforeOrdination Context triple: [Nanda, spouseBeforeOrdination, Janapadakalyāṇī]
-
A.
spouseBeforeConversion
Indicates that one person was the spouse of another prior to a specified religious or ideological conversion.
-
B.
marriageBefore
Indicates that one marriage event occurred earlier in time than another marriage event.
-
C.
spouseStatusAtMarriage
Indicates the marital status each partner held at the time their marriage to one another was formed.
-
D.
spouseLaterMarriedBy
Indicates that one’s spouse subsequently entered into a later marriage with another partner.
-
E.
spouseInQuestion
Indicates that the referenced person is the spouse of the primary entity being discussed or queried.
- 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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
| PDg | Predicate description generation | batch_69fee0b03a0c81909117dc5915d77295 |
completed | May 9, 2026, 7:22 a.m. |
Created at: May 3, 2026, 4:33 p.m.