Triple
T2504901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teapot Dome oil field |
E52554
|
entity |
| Predicate | scandalType |
P29490
|
FINISHED |
| Object | political corruption scandal |
—
|
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: political corruption scandal | Statement: [Teapot Dome oil field, scandalType, political corruption scandal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scandalType Context triple: [Teapot Dome oil field, scandalType, political corruption scandal]
-
A.
associatedScandal
chosen
Indicates a relationship where an entity is linked to, involved in, or notably connected with a particular scandal.
-
B.
accusationType
Indicates the specific category or nature of an accusation made by one party against another.
-
C.
subjectOfInquest
Indicates that an entity is the focus or target of a formal inquest or official investigative proceeding.
-
D.
controversy
Indicates a situation in which there is active disagreement, dispute, or public debate between parties over a particular issue, action, or claim.
-
E.
roleInControversy
Indicates the specific part, involvement, or function an entity has within a particular controversy or disputed situation.
- 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_69ab4957b3a88190adf968ae0c1b931c |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd65d6a988190aaaac8e98540a14f |
completed | March 7, 2026, 7:40 a.m. |
| PD | Predicate disambiguation | batch_69abd0bd996c8190ba8b9d6e4333b8d4 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.