Triple
T1576410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paulette Goddard |
E33661
|
entity |
| Predicate | marriageToBurgessMeredithStart |
P30739
|
FINISHED |
| Object | 1944 |
—
|
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: 1944 | Statement: [Paulette Goddard, marriageToBurgessMeredithStart, 1944]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageToBurgessMeredithStart Context triple: [Paulette Goddard, marriageToBurgessMeredithStart, 1944]
-
A.
marriageToHenryIIDate
Indicates the date on which an entity entered into marriage with Henry II.
-
B.
houseByMarriage
Indicates a familial or household relationship established through marriage rather than by blood or direct residence.
-
C.
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.
-
D.
marries
Indicates that one entity enters into a legally or socially recognized marital union with another entity.
-
E.
marriageDate
Indicates the specific date on which two entities entered into a marital relationship.
- 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_69a885f27a4c8190a4622252cdf54c00 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907ba63c88190b60c14dec8d1e40f |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a9607716b4819092187f8c08daaf31 |
completed | March 5, 2026, 10:52 a.m. |
Created at: March 4, 2026, 7:27 p.m.