Triple
T16601665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paydirt Pete |
E403343
|
entity |
| Predicate | thematicOccupation |
P2374
|
FINISHED |
| Object | miner |
—
|
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: miner | Statement: [Paydirt Pete, thematicOccupation, miner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thematicOccupation Context triple: [Paydirt Pete, thematicOccupation, miner]
-
A.
hasOccupationTheme
Indicates that something (such as a work or resource) centrally involves or focuses on a particular occupation or type of work as its main theme.
-
B.
occupationType
Indicates the specific kind or category of work, profession, or role that an entity performs or holds.
-
C.
subjectOccupation
chosen
Indicates that the subject holds or performs a particular job, profession, or role as their occupation.
-
D.
traditionalOccupations
Indicates that an entity is associated with occupations or jobs that are customary, long-established, or culturally traditional within a particular community or context.
-
E.
natureOfOccupation
Indicates the type or character of a person's occupation, describing what kind of work or role it is rather than who performs it.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d764574819081366374ca0c9bea |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.