Triple
T6108669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purchas his Pilgrimes |
E136176
|
entity |
| Predicate | editorOccupationOfSamuelPurchas |
P938
|
FINISHED |
| Object | clergyman |
—
|
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: clergyman | Statement: [Purchas his Pilgrimes, editorOccupationOfSamuelPurchas, clergyman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editorOccupationOfSamuelPurchas Context triple: [Purchas his Pilgrimes, editorOccupationOfSamuelPurchas, clergyman]
-
A.
authorOccupation
chosen
Indicates the professional role or job that an author holds or is associated with.
-
B.
purposeOfVoyages
Indicates the intended goals, reasons, or objectives motivating or justifying specific voyages.
-
C.
sonOccupation
Indicates that a specified occupation is the job or professional role held by a person's son.
-
D.
primaryPilgrims
Indicates that the referenced entities are the main or principal participants undertaking a pilgrimage in relation to something or someone.
-
E.
collectedBy
Indicates that one entity has gathered, acquired, or assembled another entity, typically as part of a collection or data-gathering process.
- 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_69c0087dee9881909e3655be88208c01 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b835ed48190971c3ba397ca329f |
completed | March 22, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c049f80e2081909b7d84a104cda68d |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:13 p.m.