Triple
T28430610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clark |
E715116
|
entity |
| Predicate | associatedWithOccupationHistorically |
P128477
|
FINISHED |
| Object | clerical work |
—
|
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: clerical work | Statement: [Clark, associatedWithOccupationHistorically, clerical work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithOccupationHistorically Context triple: [Clark, associatedWithOccupationHistorically, clerical work]
-
A.
historicalOccupationPattern
Indicates a recurring or characteristic pattern in the occupations held by an entity or its members over historical periods.
-
B.
historicalHolderOccupation
chosen
Indicates that an entity historically held a particular occupation or professional role.
-
C.
endedOccupationOf
Indicates that one entity brought another entity’s occupation or control of a place or position to an end.
-
D.
laterOccupationApproxDate
Indicates an approximate date or time period when a subject began a subsequent occupation or role after an earlier one.
-
E.
eraOfOccupation
Indicates the time period during which an occupation or role was held or practiced.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_6a0144c75aec81908bdd9e88f2af737a |
completed | May 11, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_6a014405a2d48190a1d58b0b907ad696 |
completed | May 11, 2026, 2:50 a.m. |
Created at: April 28, 2026, 1:39 a.m.