Triple
T25219647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ochs family |
E631925
|
entity |
| Predicate | mergedWithByMarriage |
P4942
|
FINISHED |
| Object | Sulzberger 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: Sulzberger family | Statement: [Ochs family, mergedWithByMarriage, Sulzberger family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergedWithByMarriage Context triple: [Ochs family, mergedWithByMarriage, Sulzberger family]
-
A.
marriedBy
Indicates that one entity is the officiant or authority who performs and formalizes the marriage of another entity.
-
B.
marriedInto
chosen
Indicates that one entity became connected to another’s family or group through marriage, rather than by birth or prior membership.
-
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.
membershipChangeOnMarriage
Indicates a change in an entity’s membership status in some group or organization that occurs as a direct result of a marriage event.
-
E.
spouseLaterMarriedBy
Indicates that one’s spouse subsequently entered into a later marriage with another partner.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47b914fe08190b104ecc2583ce1f7 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 1:02 p.m.