Triple
T23824561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bill Gaither |
E589330
|
entity |
| Predicate | hasPartnerInDuo |
P44416
|
FINISHED |
| Object | Gloria Gaither |
—
|
NE NERFINISHED |
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: Gloria Gaither | Statement: [Bill Gaither, hasPartnerInDuo, Gloria Gaither]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartnerInDuo Context triple: [Bill Gaither, hasPartnerInDuo, Gloria Gaither]
-
A.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
-
B.
hasDoublesPartner
chosen
Indicates that one entity serves as the doubles partner of another in a paired or team-based activity or sport.
-
C.
hasExPartner
Indicates that one entity was formerly in a romantic or intimate partnership with another entity, but that relationship has ended.
-
D.
hasPartnerInSport
Indicates that one entity has another entity as a partner with whom they jointly participate in a sport or sporting activity.
-
E.
hasPartnerInWork
Indicates that one entity collaborates professionally or is partnered with another entity in a work-related context.
- 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_69e25d1922d481909cab567c06a802ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7f04bdc8190842a287a86b60d3a |
completed | April 29, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8 p.m.