Triple
T30584202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kakusandha Buddha |
E778459
|
entity |
| Predicate | chiefPatronMale |
P44585
|
FINISHED |
| Object | Accuta |
—
|
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: Accuta | Statement: [Kakusandha Buddha, chiefPatronMale, Accuta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chiefPatronMale Context triple: [Kakusandha Buddha, chiefPatronMale, Accuta]
-
A.
chief
Indicates that one entity holds the highest-ranking leadership or authoritative position over another entity or within a specified context.
-
B.
chiefSaintOf
Indicates that one entity serves as the principal or primary patron saint associated with another entity (such as a place, group, or institution).
-
C.
primaryPatron
chosen
Indicates that one entity serves as the main or chief supporter, sponsor, or benefactor of another entity.
-
D.
chiefLieutenantOf
Indicates that one person serves as the primary subordinate or top-ranking assistant to another leader or authority figure.
-
E.
patron of
Indicates a supportive relationship in which one entity provides sponsorship, protection, or backing to another, often enabling its activities or development.
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:23 p.m.