Triple
T27763171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Livanos family |
E701527
|
entity |
| Predicate | hasMaritalConnectionWith |
P195567
|
FINISHED |
| Object | Onassis 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: Onassis family | Statement: [Livanos family, hasMaritalConnectionWith, Onassis family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaritalConnectionWith Context triple: [Livanos family, hasMaritalConnectionWith, Onassis family]
-
A.
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.
-
B.
hasMemberSpouseConnection
Indicates a relationship where one entity is a spouse of a member associated with the other entity.
-
C.
isMarriedToA
Indicates that one entity is legally and socially bound in marriage to another specific entity.
-
D.
marriageLinkedBranch
chosen
Indicates a connection between two branches or lineages that is established or traced through a marriage relationship.
-
E.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fe86cad5108190b0164b8bc6fc23ea |
completed | May 9, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69fe83c0c9888190b6fc40c7f727b569 |
completed | May 9, 2026, 12:45 a.m. |
Created at: April 27, 2026, 4:28 p.m.