Triple
T13559349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thaw–White murder case |
E323863
|
entity |
| Predicate | involvedProfession |
P69514
|
FINISHED |
| Object | architect |
—
|
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: architect | Statement: [Thaw–White murder case, involvedProfession, architect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedProfession Context triple: [Thaw–White murder case, involvedProfession, architect]
-
A.
includesProfession
chosen
Indicates that one entity’s set of attributes, roles, or members contains a specific profession as part of it.
-
B.
relatedProfession
Indicates that two entities have professions that are connected or associated in some meaningful way, such as being in the same field, industry, or professional domain.
-
C.
memberProfession
Indicates that a member or individual holds or practices a particular profession or occupation.
-
D.
leftProfession
Indicates that an entity has stopped or abandoned a particular profession or occupation they previously held.
-
E.
subjectOccupation
Indicates that the subject holds or performs a particular job, profession, or role as their occupation.
- 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae13bec4819084c1770638c00ed9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:47 p.m.