Triple
T33878883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitcross district |
E868429
|
entity |
| Predicate | hasOccupationOfResident |
P177859
|
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: [Whitcross district, hasOccupationOfResident, clergyman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOccupationOfResident Context triple: [Whitcross district, hasOccupationOfResident, clergyman]
-
A.
endedOccupationOf
Indicates that one entity brought another entity’s occupation or control of a place or position to an end.
-
B.
significantResidentOccupation
Indicates that a resident’s occupation is notably important or defining in the context of their residence or community.
-
C.
ownerOccupation
Indicates that the occupation or job role of an entity that owns something is being specified or described.
-
D.
hasOccupationOfDesignee
Indicates that one entity serves as the designated or appointed holder of an occupation or role for another entity.
-
E.
hasNonHumanResident
Indicates that a place or location is inhabited or occupied by one or more non-human entities.
- 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_69f34995b81c8190acdb45cea5a10eff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f70519f114819080659840c04d7911 |
completed | May 3, 2026, 8:19 a.m. |
Created at: May 1, 2026, 1:48 a.m.