Triple
T37892606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christina Haack |
E945187
|
entity |
| Predicate | marriageToAntAnsteadStart |
P196271
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Christina Haack, marriageToAntAnsteadStart, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageToAntAnsteadStart Context triple: [Christina Haack, marriageToAntAnsteadStart, 2018]
-
A.
marriageToAndrewConradStart
Indicates the point in time when an entity’s marriage to Andrew Conrad begins.
-
B.
laterMarriedIn
Indicates that two entities became married at a later time relative to a previously referenced event or marital status.
-
C.
laterMarriedBy
Indicates that an entity is married by another entity at a later point in time relative to some prior reference event or relationship.
-
D.
marriedOn
Indicates that a marriage event took place on a specific date for the related entities.
-
E.
isUsuallyMarriedTo
Indicates that one entity is typically or customarily married to another entity under normal or common circumstances.
- 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fe189f2ea48190b8c4718f1353970e |
completed | May 8, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4:19 p.m.