Triple
T32921774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emma Smith |
E842161
|
entity |
| Predicate | roleInScripturalProjects |
P120579
|
FINISHED |
| Object | scribe and assistant |
—
|
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: scribe and assistant | Statement: [Emma Smith, roleInScripturalProjects, scribe and assistant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInScripturalProjects Context triple: [Emma Smith, roleInScripturalProjects, scribe and assistant]
-
A.
scriptureContributedTo
Indicates that an entity played a role in creating, authoring, or otherwise contributing content to a particular scripture or sacred text.
-
B.
hasScripturalRole
chosen
Indicates that an entity holds a specific role, function, or position within a scriptural or religious text.
-
C.
associatedWithScriptureActivity
Indicates a relationship where an entity is connected to, involved in, or participates in an activity related to scripture.
-
D.
scripturalFunction
Indicates the role or purpose that a text or passage serves within a scriptural or religious context.
-
E.
inScripture
Indicates that something is mentioned, described, or referenced within a scriptural or sacred 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0062e6bd788190a7b4f3e5befb5cbb |
completed | May 10, 2026, 10:50 a.m. |
| PD | Predicate disambiguation | batch_6a0061989d188190b4815b2de3e8676f |
completed | May 10, 2026, 10:44 a.m. |
Created at: May 1, 2026, 1:19 a.m.