Triple
T9915881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shammah |
E185866
|
entity |
| Predicate | appearsInNarrative |
P38554
|
FINISHED |
| Object | anointing of David by Samuel |
—
|
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: anointing of David by Samuel | Statement: [Shammah, appearsInNarrative, anointing of David by Samuel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInNarrative Context triple: [Shammah, appearsInNarrative, anointing of David by Samuel]
-
A.
appearsInShortStoryBy
Indicates that one entity is a character, element, or subject that appears within a short story authored by another entity.
-
B.
hasPartInNarrative
chosen
Indicates that one entity plays a role or participates as a component within the storyline or structure of another narrative entity.
-
C.
appearsIn
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
D.
containsNarrativeOf
Indicates that one entity includes or presents the story, account, or narrative content of another entity.
-
E.
narrativePresence
Indicates that an entity appears or is involved within the narrative or storyline of another entity.
- 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_69ca829b45f481909040f7b99a1976ed |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb53d5be48190ab47e152760d5e2c |
completed | April 2, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:42 p.m.