Triple
T30873003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wentworth-Fitzwilliam family |
E786393
|
entity |
| Predicate | mergedThroughMarriage |
P4942
|
FINISHED |
| Object | Wentworth family |
—
|
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: Wentworth family | Statement: [Wentworth-Fitzwilliam family, mergedThroughMarriage, Wentworth family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergedThroughMarriage Context triple: [Wentworth-Fitzwilliam family, mergedThroughMarriage, Wentworth family]
-
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.
marriedAfter
Indicates that one marriage occurred later in time than another specified marriage.
-
D.
hasMarriedSurname
Indicates that a person’s current surname is the one they adopted through marriage.
-
E.
connectedThroughMarriageVia
Indicates that two entities are related to each other by a marital connection that is mediated through one or more intermediate spouses or in-laws, rather than by a direct marriage between them.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f691d32690819096a06d9a3dfb9e2d |
completed | May 3, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:48 p.m.