Triple
T29076089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuppence Beresford |
E735943
|
entity |
| Predicate | partnerInDetectionWith |
P120802
|
FINISHED |
| Object | Tommy Beresford |
—
|
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: Tommy Beresford | Statement: [Tuppence Beresford, partnerInDetectionWith, Tommy Beresford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerInDetectionWith Context triple: [Tuppence Beresford, partnerInDetectionWith, Tommy Beresford]
-
A.
partnerInDiscovery
Indicates that two or more entities collaborated as partners in making a particular discovery.
-
B.
partnerInInvestigationWith
chosen
Indicates that two entities are collaborating as partners in the same investigation.
-
C.
partnerInActWith
Indicates that two or more entities jointly participate as partners in carrying out the same act or action.
-
D.
partnerInRuleWith
Indicates that two or more entities jointly participate as partners in establishing, enforcing, or being governed by the same rule or regulatory framework.
-
E.
partnerInOrganizationWith
Indicates that two entities are associated as partners within the same organization or organizational context.
- 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_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 28, 2026, 10:23 a.m.