Triple
T38018359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pudgalavada traditions |
E948554
|
entity |
| Predicate | viewOnRebirth |
P193869
|
FINISHED |
| Object | rebirth involves continuity of a person |
—
|
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: rebirth involves continuity of a person | Statement: [Pudgalavada traditions, viewOnRebirth, rebirth involves continuity of a person]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOnRebirth Context triple: [Pudgalavada traditions, viewOnRebirth, rebirth involves continuity of a person]
-
A.
viewOnResurrection
Indicates a subject’s doctrinal or personal stance regarding the concept of resurrection.
-
B.
viewOnIncarnation
Indicates a relationship where an entity holds a particular belief, stance, or doctrinal position regarding the concept of incarnation.
-
C.
viewOnLife
Indicates a person's general attitude, perspective, or philosophy regarding life.
-
D.
viewOnRevelation
Indicates the stance or interpretation an entity holds regarding the nature, source, or authority of divine revelation.
-
E.
viewOnCreation
Indicates that an entity is viewed or accessed immediately at the moment it is created.
- 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
| PDg | Predicate description generation | batch_69fd57b9cdec81908536c4159e375931 |
completed | May 8, 2026, 3:25 a.m. |
Created at: May 3, 2026, 4:20 p.m.