Triple
T25016589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard le Breton |
E626150
|
entity |
| Predicate | co-perpetrator |
P21638
|
FINISHED |
| Object | Hugh de Morville |
—
|
NE NERFINISHED |
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: Hugh de Morville | Statement: [Richard le Breton, co-perpetrator, Hugh de Morville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: co-perpetrator Context triple: [Richard le Breton, co-perpetrator, Hugh de Morville]
-
A.
numberOfCoPerpetrators
Indicates the quantity of additional perpetrators who jointly participated in committing the same act or offense.
-
B.
partnerInCrime
chosen
Indicates a relationship where two or more entities collaborate closely in committing or planning wrongful, illicit, or mischievous acts together.
-
C.
perpetratorType
Indicates the classification or category of the entity that carried out or is responsible for a harmful, illegal, or otherwise wrongful act.
-
D.
perpetratorStatus
Indicates the role or condition of an individual in relation to committing or being responsible for a specific harmful or criminal act.
-
E.
perpetratedBy
Indicates that an action, event, or wrongdoing was carried out or caused by a particular agent or entity.
- 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_69e2ff27755881908490178e83701160 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:06 a.m.