Triple
T38659265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchess of Bedford |
E939983
|
entity |
| Predicate | transferOn |
P201666
|
FINISHED |
| Object | marriage to the Duke of Bedford |
—
|
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: marriage to the Duke of Bedford | Statement: [Duchess of Bedford, transferOn, marriage to the Duke of Bedford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferOn Context triple: [Duchess of Bedford, transferOn, marriage to the Duke of Bedford]
-
A.
transferBetween
Indicates a movement or handover of something from one entity to another, typically changing its location, ownership, or control between them.
-
B.
transferAfter
Indicates that one entity transfers something to another entity only after a specified event or condition has occurred.
-
C.
transferType
Indicates the specific method or category of how something is transferred from one entity to another.
-
D.
transferEvent
Indicates an event in which something is moved, handed over, or reassigned from one entity to another.
-
E.
transferImplementedBy
Indicates that a specific transfer process or specification is realized or carried out by a particular implementation or mechanism.
- 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_69f76ede49648190a48bfe47032a05a3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0010e46d948190a51111b5270fade7 |
completed | May 10, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_6a001061d34c8190bfe73f3d7c061eb7 |
completed | May 10, 2026, 4:58 a.m. |
| PDg | Predicate description generation | batch_6a0010e304a08190a4d0a4fa11a9a3b3 |
completed | May 10, 2026, 5 a.m. |
Created at: May 3, 2026, 4:33 p.m.