Triple
T8027341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columba Bush |
E186886
|
entity |
| Predicate | metSpouseYear |
P29935
|
FINISHED |
| Object | 1971 |
—
|
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: 1971 | Statement: [Columba Bush, metSpouseYear, 1971]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metSpouseYear Context triple: [Columba Bush, metSpouseYear, 1971]
-
A.
metSpouseAt
chosen
Indicates that one person first encountered or became acquainted with their spouse at a particular place, event, or time.
-
B.
spouseOfSince
Indicates that two individuals are spouses and specifies the date or time from which their marital relationship has been in effect.
-
C.
metSpouseThrough
Indicates that one person became acquainted with and subsequently married their spouse as a result of a particular intermediary person, event, place, or context.
-
D.
spouseExecutionYear
Indicates the calendar year in which a person's spouse was executed.
-
E.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
- 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_69ca82ad4e2c8190a693e3c9e30fe66f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3eccacb0819082f7c3d6fd48e3c4 |
completed | March 31, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:21 p.m.