Triple
T30876044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samuel the Lamanite |
E786477
|
entity |
| Predicate | preachingLocationDetail |
P11131
|
FINISHED |
| Object | upon the wall of the city of Zarahemla |
—
|
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: upon the wall of the city of Zarahemla | Statement: [Samuel the Lamanite, preachingLocationDetail, upon the wall of the city of Zarahemla]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preachingLocationDetail Context triple: [Samuel the Lamanite, preachingLocationDetail, upon the wall of the city of Zarahemla]
-
A.
preachesFrom
chosen
Indicates that a person delivers a sermon, teaching, or religious message using a particular text, source, or location as the basis.
-
B.
liturgicalLocation
Indicates the place or setting where a liturgical act, ritual, or religious service occurs.
-
C.
congregationalLocation
Indicates the place where a congregation or group regularly gathers or meets.
-
D.
mainPreachingSite
Indicates the primary location where an entity most regularly or prominently conducts its preaching activities.
-
E.
placeOfWorshipLocation
Indicates the location where a particular place of worship is situated or found.
- 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_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. |
Created at: April 29, 2026, 8:48 p.m.