Triple
T11674278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Śāriputra |
E277451
|
entity |
| Predicate | dialogueRoleIn |
P9564
|
FINISHED |
| Object | Heart Sūtra opening interlocutor |
—
|
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: Heart Sūtra opening interlocutor | Statement: [Śāriputra, dialogueRoleIn, Heart Sūtra opening interlocutor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dialogueRoleIn Context triple: [Śāriputra, dialogueRoleIn, Heart Sūtra opening interlocutor]
-
A.
roleInDialogue
chosen
Indicates that an entity participates in a dialogue with a specific conversational role (e.g., speaker, listener, moderator) relative to other participants.
-
B.
roleInScene
Indicates that an entity participates in a particular scene with a specific role or function within that scene.
-
C.
playRoleIn
Indicates that an entity participates in or performs a specific function, character, or part within an event, context, or system.
-
D.
speakerRole
Indicates the functional role or capacity in which an entity is acting as a speaker within a communicative event.
-
E.
roleInVox
Indicates that an entity holds a specific role or function within a Vox-related context, such as a project, system, or organization named or described as "Vox."
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a443b6848190a1eb6825fbc49d08 |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a77e6e88190b7519100bde76575 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.