Triple
T30876047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samuel the Lamanite |
E786477
|
entity |
| Predicate | divineProtection |
P170591
|
FINISHED |
| Object | arrows could not hit him |
—
|
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: arrows could not hit him | Statement: [Samuel the Lamanite, divineProtection, arrows could not hit him]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divineProtection Context triple: [Samuel the Lamanite, divineProtection, arrows could not hit him]
-
A.
divineSign
Indicates that one entity serves as a supernatural or sacred omen, message, or signal from a divine source to another entity.
-
B.
divineStatus
Indicates that an entity possesses a sacred, godlike, or religiously exalted status in relation to another entity or within a given belief system.
-
C.
divineAgent
Indicates that the related entity acts as a deity or supernatural agent responsible for causing or overseeing the associated event or state.
-
D.
spiritualPatron
Indicates that one entity serves as a guiding or protective spiritual figure or patron for another entity.
-
E.
blessedBy
Indicates that one entity has conferred a blessing, favor, or sacred endorsement upon another entity.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f691d6a90081908726a2218a51dc25 |
completed | May 3, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68fb914b88190b0cad83ea9fe9dfc |
completed | May 2, 2026, 11:58 p.m. |
Created at: April 29, 2026, 8:48 p.m.