Triple
T15926938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahershalalhashbaz |
E386226
|
entity |
| Predicate | hasScripturalRole |
P120579
|
FINISHED |
| Object | name of Isaiah's son |
—
|
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: name of Isaiah's son | Statement: [Mahershalalhashbaz, hasScripturalRole, name of Isaiah's son]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScripturalRole Context triple: [Mahershalalhashbaz, hasScripturalRole, name of Isaiah's son]
-
A.
hasReligiousRoleEquivalent
Indicates that two religious roles are considered functionally or hierarchically equivalent within or across religious traditions.
-
B.
religiousTextRole
Indicates the specific role or function that a religious text has in relation to a person, group, practice, or tradition.
-
C.
hasScripture
Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
-
D.
theologicalRole
Indicates a relationship where an entity holds or is assigned a specific function, office, or status within a theological or religious framework.
-
E.
liturgicalRole
Indicates the specific function or position an entity holds within a religious or liturgical context.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69e172b213e481909ee0c05e16229a26 |
completed | April 16, 2026, 11:37 p.m. |
Created at: April 10, 2026, 4:52 a.m.