Triple
T12082489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbara Cushing Mortimer |
E287713
|
entity |
| Predicate | hasMarriedInto |
P4942
|
FINISHED |
| Object | wealthy families |
—
|
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: wealthy families | Statement: [Barbara Cushing Mortimer, hasMarriedInto, wealthy families]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarriedInto Context triple: [Barbara Cushing Mortimer, hasMarriedInto, wealthy families]
-
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.
hasMarriage
Indicates a marital relationship exists between the two entities, specifying that they are or were legally married to each other.
-
C.
marriedIn
Indicates that two entities entered into a marital relationship at a specific place or within a particular jurisdiction.
-
D.
marriedBy
Indicates that one entity is the officiant or authority who performs and formalizes the marriage of another entity.
-
E.
marriedAfter
Indicates that one marriage occurred later in time than another specified marriage.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9178ad99c8190a54777b9bbe998bc |
completed | April 10, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69d915000454819089fee00022055599 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:48 p.m.