Triple
T14189939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marc Mezvinsky |
E351684
|
entity |
| Predicate | hasStepSiblings |
P29991
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Marc Mezvinsky, hasStepSiblings, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStepSiblings Context triple: [Marc Mezvinsky, hasStepSiblings, true]
-
A.
hasStepSibling
chosen
Indicates that one person is the step-sibling of another, meaning they are related through the marriage of their parents rather than by blood or adoption.
-
B.
hasStepchildren
Indicates that one person has stepchildren, meaning children of their spouse or partner from a previous relationship.
-
C.
hasStepFamily
Indicates that one person is related to another as a member of a stepfamily, such as a stepparent, stepchild, or stepsibling, through marriage rather than blood or adoption.
-
D.
hasStep
Indicates that one entity includes, is composed of, or is associated with a specific step or stage in a process involving another entity.
-
E.
hasStepsLeadingTo
Indicates that one location or object is connected to another by a set of steps or a staircase leading toward it.
- 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_69d827894ac0819097803e57f3227b23 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61df628c8190ba3f557e2128dce5 |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:03 a.m.