Triple
T30584201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kakusandha Buddha |
E778459
|
entity |
| Predicate | chiefAttendant |
P170469
|
FINISHED |
| Object | Buddhija |
—
|
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: Buddhija | Statement: [Kakusandha Buddha, chiefAttendant, Buddhija]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chiefAttendant Context triple: [Kakusandha Buddha, chiefAttendant, Buddhija]
-
A.
chief
Indicates that one entity holds the highest-ranking leadership or authoritative position over another entity or within a specified context.
-
B.
chiefCharge
Indicates that one entity holds the primary responsibility, leadership, or authority over another entity or activity.
-
C.
crewChief
Indicates that one person serves as the lead or supervising crew chief responsible for directing and managing another person or group in an operational context.
-
D.
principalInterlocutor
Indicates that one entity serves as the main or primary conversational partner or speaker in an interaction with another entity.
-
E.
chiefLieutenantOf
Indicates that one person serves as the primary subordinate or top-ranking assistant to another leader or authority figure.
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 29, 2026, 8:23 p.m.