Triple
T24706558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Will Hopoate |
E611907
|
entity |
| Predicate | tookReligiousMissionBreak |
P157012
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Will Hopoate, tookReligiousMissionBreak, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookReligiousMissionBreak Context triple: [Will Hopoate, tookReligiousMissionBreak, yes]
-
A.
precededOnPilgrimageBy
Indicates that one entity went on a pilgrimage earlier in time than another, such that the first entity’s pilgrimage occurred before the second’s.
-
B.
hasNotableMissionary
Indicates that an entity is associated with, or has, a notable missionary linked to it.
-
C.
tookReligiousVows
Indicates that an entity formally committed to a religious life by taking recognized vows within a religious tradition.
-
D.
isMissionary
Indicates that an entity serves as a missionary, engaging in religious outreach or proselytizing activities toward others.
-
E.
pilgrimageSince
Indicates that an entity has been engaged in or committed to a pilgrimage starting from a specified point in time.
- 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_69e2c4d9c24c8190a3712d74327f0c6e |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f410fc18808190b4e47d5a71d3a126 |
completed | May 1, 2026, 2:33 a.m. |
Created at: April 18, 2026, 3:24 a.m.