Triple
T35620590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clinton email controversy |
E1029301
|
entity |
| Predicate | officeHolderInvolved |
P32048
|
FINISHED |
| Object | Hillary Clinton |
—
|
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: Hillary Clinton | Statement: [Clinton email controversy, officeHolderInvolved, Hillary Clinton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeHolderInvolved Context triple: [Clinton email controversy, officeHolderInvolved, Hillary Clinton]
-
A.
involvesOfficeHolder
chosen
Indicates that the relationship or action includes or pertains to a person currently holding a specific office or official position.
-
B.
officeHolderIs
Indicates that one entity serves as the office holder (e.g., official or position occupant) of another entity, such as an office, role, or institution.
-
C.
officeHolderMayBe
Indicates that a specified person is permitted or eligible to hold a particular office or position.
-
D.
involvedOfficer
Indicates that an officer participated in, was connected to, or played a role in a particular incident, case, or event.
-
E.
officeHoldersParticipateIn
Indicates that individuals holding an office take part in or are involved in a specified event, activity, or process.
- 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_69f76e0709408190bbe322bf1707ef6b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffef812da48190b875a7376b24f92d |
completed | May 10, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69ffedecd580819097851b1473fdd6ed |
completed | May 10, 2026, 2:31 a.m. |
Created at: May 3, 2026, 4:05 p.m.