Triple
T24371497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parley P. Pratt |
E614343
|
entity |
| Predicate | missionaryWorkArea |
P20194
|
FINISHED |
| Object | United States |
—
|
NE NERFINISHED |
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: United States | Statement: [Parley P. Pratt, missionaryWorkArea, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionaryWorkArea Context triple: [Parley P. Pratt, missionaryWorkArea, United States]
-
A.
missionaryRegion
chosen
Indicates that an entity carries out or is associated with missionary activities within a specified geographic region.
-
B.
ministryArea
Indicates that one entity is the geographic or administrative area over which a ministry or ministerial body has responsibility or jurisdiction.
-
C.
missionaryOrganization
Indicates that an entity is a religious or faith-based organization dedicated to missionary work or activities.
-
D.
placeOfEvangelisticActivity
Indicates the location where evangelistic or missionary activities are carried out.
-
E.
servesDiocesesIn
Indicates that an ecclesiastical jurisdiction, organization, or office provides services, support, or oversight to one or more specified dioceses.
- 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_69e2d7e1e010819098b95eb3f905943d |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2938b95188190b8f7ee1098c6088a |
completed | April 29, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:02 a.m.