Triple
T33033894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eva Pogner |
E845249
|
entity |
| Predicate | betrothedByContest |
P175722
|
FINISHED |
| Object | winner of the mastersinging contest |
—
|
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: winner of the mastersinging contest | Statement: [Eva Pogner, betrothedByContest, winner of the mastersinging contest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: betrothedByContest Context triple: [Eva Pogner, betrothedByContest, winner of the mastersinging contest]
-
A.
rivalForMarriageOf
Indicates that one entity is a romantic competitor with another entity for the opportunity to marry a specific third entity.
-
B.
betrothedByFatherTo
Indicates that an individual is formally promised or given in marriage to another person by their father’s decision or arrangement.
-
C.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
D.
betrothalType
Indicates the specific kind or category of engagement or promised marriage relationship that exists between two parties.
-
E.
betrothalEnd
Indicates that a previously established engagement or betrothal between two parties has been terminated or dissolved.
- 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_69f34951348c8190b56746b0a7018182 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: May 1, 2026, 1:24 a.m.