Triple
T29150547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Spector |
E738894
|
entity |
| Predicate | hasProfessionCover |
P199596
|
FINISHED |
| Object | grief counsellor |
—
|
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: grief counsellor | Statement: [Paul Spector, hasProfessionCover, grief counsellor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProfessionCover Context triple: [Paul Spector, hasProfessionCover, grief counsellor]
-
A.
workCoverage
Indicates that one entity’s work or responsibilities extend to, include, or provide coverage for another entity, area, or time period.
-
B.
coversOccupation
Indicates that one entity provides information about, includes, or pertains to another entity’s occupation or professional role.
-
C.
hasProfessionalSection
Indicates that an entity includes or is associated with a designated professional section, division, or category within its structure or content.
-
D.
hasProfessionSetting
Indicates that an entity’s professional activity or role is carried out within a particular setting or environment.
-
E.
includesProfession
Indicates that one entity’s set of attributes, roles, or members contains a specific profession as part of it.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69ff48199b1c8190bb05872f8a4f4673 |
completed | May 9, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69ff4746b1cc8190854f70a124df7d04 |
completed | May 9, 2026, 2:40 p.m. |
| PDg | Predicate description generation | batch_69ff4818bb288190b4a27576fad18e23 |
completed | May 9, 2026, 2:43 p.m. |
Created at: April 28, 2026, 11:42 a.m.