Triple
T30046888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gretchen Johnson |
E763478
|
entity |
| Predicate | metSpouseAs |
P29935
|
FINISHED |
| Object | contestant |
—
|
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: contestant | Statement: [Gretchen Johnson, metSpouseAs, contestant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metSpouseAs Context triple: [Gretchen Johnson, metSpouseAs, contestant]
-
A.
metSpouseAt
chosen
Indicates that one person first encountered or became acquainted with their spouse at a particular place, event, or time.
-
B.
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.
-
C.
spouseOfType
Indicates that one entity is the spouse of another, specifying the type or role of that spousal relationship.
-
D.
spouseOfWork
Indicates that one person is the spouse of another specifically in the context of their workplace or professional environment.
-
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_69f22470a89c8190be7273297c0e0d19 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67a12ee4881908418a2814ac05db8 |
completed | May 2, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 6:54 p.m.