Triple
T34358398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tedeschi Trucks Band |
E881801
|
entity |
| Predicate | spouseLeaders |
P195786
|
FINISHED |
| Object | Derek Trucks and Susan Tedeschi |
—
|
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: Derek Trucks and Susan Tedeschi | Statement: [Tedeschi Trucks Band, spouseLeaders, Derek Trucks and Susan Tedeschi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseLeaders Context triple: [Tedeschi Trucks Band, spouseLeaders, Derek Trucks and Susan Tedeschi]
-
A.
spouseOfLeader
Indicates that one entity is the married partner (spouse) of another entity who holds a leadership position.
-
B.
spouseOfHouse
Indicates a marital relationship between a person and a householder or head of household.
-
C.
spouseOfHeadOfState
Indicates that one person is the spouse (married partner) of a head of state.
-
D.
spouseOffice
Indicates that one entity holds an office or position that is associated with, or held by, the spouse of another entity.
-
E.
spouseOfCountry
Indicates that an entity is the spouse or marital partner of a person who is associated with, represents, or is from a specified country.
- 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_69f349bd06008190904c2f86c42749e3 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69fde5d677b88190bc904e6df8617c18 |
completed | May 8, 2026, 1:32 p.m. |
Created at: May 1, 2026, 1:58 a.m.