Triple
T33837886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mezvinsky family |
E867282
|
entity |
| Predicate | hasMaritalTieWith |
P45367
|
FINISHED |
| Object | Clinton 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: Clinton family | Statement: [Mezvinsky family, hasMaritalTieWith, Clinton family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaritalTieWith Context triple: [Mezvinsky family, hasMaritalTieWith, Clinton family]
-
A.
isMarriedToA
Indicates that one entity is legally and socially bound in marriage to another specific entity.
-
B.
hasMaritalRelationshipType
Indicates the specific type or nature of the marital relationship that exists between two entities.
-
C.
marriedBy
Indicates that one entity is the officiant or authority who performs and formalizes the marriage of another entity.
-
D.
hasMarriage
chosen
Indicates a marital relationship exists between the two entities, specifying that they are or were legally married to each other.
-
E.
isUsuallyMarriedTo
Indicates that one entity is typically or customarily married to another entity under normal or common circumstances.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0141fceb908190863778741bd4487d |
completed | May 11, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_6a0141a9628c819090c0b24ce052a2fb |
completed | May 11, 2026, 2:40 a.m. |
Created at: May 1, 2026, 1:47 a.m.