Triple
T19850646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andy Cohen |
E476982
|
entity |
| Predicate | usedSurrogacy |
P137571
|
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: [Andy Cohen, usedSurrogacy, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedSurrogacy Context triple: [Andy Cohen, usedSurrogacy, true]
-
A.
hasSurrogatePregnancyFor
Indicates that one entity is carrying a pregnancy on behalf of another entity, typically with the intention of giving the resulting child to that other entity.
-
B.
adoptedThrough
Indicates that an adoption relationship was established or carried out by means of a specified process, channel, or intermediary.
-
C.
usedMarriageFor
Indicates that one party employed marriage as a means or tool to achieve some goal, benefit, or ulterior purpose involving another party.
-
D.
adoptiveParent
Indicates that one entity is the legally recognized parent of another through adoption rather than biological descent.
-
E.
providedSpermDonorFor
Indicates that one entity served as the sperm donor used for another entity’s conception or reproductive process.
- F. None of above. chosen
Provenance (4 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65867b5408190bbd12ca567c4705f |
completed | April 20, 2026, 4:46 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:51 p.m.