Triple
T19034635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchess of Montpensier |
E465833
|
entity |
| Predicate | transferredByMarriage |
P4942
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Duchess of Montpensier, transferredByMarriage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferredByMarriage Context triple: [Duchess of Montpensier, transferredByMarriage, yes]
-
A.
marriedInto
chosen
Indicates that one entity became connected to another’s family or group through marriage, rather than by birth or prior membership.
-
B.
marriedBy
Indicates that one entity is the officiant or authority who performs and formalizes the marriage of another entity.
-
C.
formedByMarriageOf
Indicates that something (typically a family, union, or legal entity) comes into existence as a result of the marriage between two entities.
-
D.
takenFromHusbandBy
Indicates that something previously belonging to a husband was removed or seized by another specified party.
-
E.
takenFromSecondHusbandBy
Indicates that something or someone was removed, seized, or otherwise taken away from a second husband by another party.
- 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d74295b88190b1c4621735a06223 |
completed | April 20, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69e4a3001e388190aa6057266514e75a |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.