Triple
T30589502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Biden |
E778611
|
entity |
| Predicate | hasRelativeOfficeholder |
P65432
|
FINISHED |
| Object | Joe Biden |
—
|
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: Joe Biden | Statement: [James Biden, hasRelativeOfficeholder, Joe Biden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelativeOfficeholder Context triple: [James Biden, hasRelativeOfficeholder, Joe Biden]
-
A.
relativeOfPoliticalOfficeHolder
chosen
Indicates that one entity is a family member or relative of another entity who holds or has held a political office.
-
B.
hasDescendantInOffice
Indicates that one entity has a descendant who holds or has held a particular office or official position.
-
C.
hasListOfOfficeHolders
Indicates that an entity is associated with a collection or record enumerating the individuals who have held a particular office or position.
-
D.
hasHistoricalOfficeHolder
Indicates that an office, position, or role has been held by a specific person at some point in the past.
-
E.
involvesOfficeHolder
Indicates that the relationship or action includes or pertains to a person currently holding a specific office or official position.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a008e29f76881908e656dbbd7fceea3 |
completed | May 10, 2026, 1:54 p.m. |
| PD | Predicate disambiguation | batch_6a008dc01b308190bc26e69814692f82 |
completed | May 10, 2026, 1:53 p.m. |
Created at: April 29, 2026, 8:24 p.m.