Triple
T1100862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heman the Ezrahite |
E24375
|
entity |
| Predicate | textualRole |
P11527
|
FINISHED |
| Object | superscription figure in Psalm 88 |
—
|
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: superscription figure in Psalm 88 | Statement: [Heman the Ezrahite, textualRole, superscription figure in Psalm 88]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textualRole Context triple: [Heman the Ezrahite, textualRole, superscription figure in Psalm 88]
-
A.
roleInText
chosen
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
B.
typographicRole
Indicates the specific typographic function or role that an element plays within written or printed content.
-
C.
displayRole
Indicates the role or position an entity holds in the context of how it is presented or shown in a display.
-
D.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
E.
literaryRole
Indicates the specific narrative or functional role an entity holds within a literary work or text.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9c079f48190a0e0ddda182f7a01 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b745ef3481909a7ce4647c8567b3 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:43 p.m.