Triple
T6638408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William of Sens |
E150516
|
entity |
| Predicate | beganWorkOn |
P19545
|
FINISHED |
| Object | Canterbury Cathedral choir after the 1174 fire |
—
|
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: Canterbury Cathedral choir after the 1174 fire | Statement: [William of Sens, beganWorkOn, Canterbury Cathedral choir after the 1174 fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganWorkOn Context triple: [William of Sens, beganWorkOn, Canterbury Cathedral choir after the 1174 fire]
-
A.
occupationBegan
Indicates the point in time when an entity started holding a particular occupation or job.
-
B.
began
chosen
Indicates that one entity initiated or started an action, event, or state involving another entity or context.
-
C.
collaborationStartWork
Indicates the point in time when a collaborative effort between entities begins or is initiated.
-
D.
useBegan
Indicates that an entity initiated or started using another entity or resource at a particular point in time.
-
E.
workOn
Indicates that an agent is actively engaged in performing tasks or making progress on a particular project, object, or assignment.
- 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_69c687f0ceb08190bf40807bfc605fa5 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c308a08881908501c862b3029321 |
completed | March 27, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c6ad024860819084b9b535b136ede6 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 2 p.m.