Triple
T24677535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bill Clinton–Paula Jones scandal |
E611029
|
entity |
| Predicate | defendantPositionAtFiling |
P55568
|
FINISHED |
| Object | President of the United States |
—
|
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: President of the United States | Statement: [Bill Clinton–Paula Jones scandal, defendantPositionAtFiling, President of the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defendantPositionAtFiling Context triple: [Bill Clinton–Paula Jones scandal, defendantPositionAtFiling, President of the United States]
-
A.
defendantPosition
chosen
Indicates the role, stance, or location that a defendant holds within a legal case or proceeding.
-
B.
placeOfFiling
Indicates the location or jurisdiction where a legal document, case, or claim is formally submitted or recorded.
-
C.
defendantStatus
Indicates the legal condition or standing of a defendant within a judicial or law-enforcement process.
-
D.
defendantLocation
Indicates the place or jurisdiction where the defendant is located or resides in relation to a legal matter.
-
E.
defendant
Indicates that an entity is the party accused or sued in a legal action or proceeding.
- 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_69e2c4d5c2dc8190ac857dea25ec6ce9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:06 a.m.