Triple
T3036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herbert Hoover |
E56
|
entity |
| Predicate | ranForOffice |
P355
|
FINISHED |
| Object | 1932 United States presidential election |
—
|
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: 1932 United States presidential election | Statement: [Herbert Hoover, ranForOffice, 1932 United States presidential election]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ranForOffice Context triple: [Herbert Hoover, ranForOffice, 1932 United States presidential election]
-
A.
leftOffice
Indicates that an entity ceased holding or performing the duties of a particular office or position.
-
B.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
C.
fieldOfWork
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
-
D.
format
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
E.
legalForm
Indicates the specific legal structure or organizational type under which an entity is formally constituted and recognized by law.
- 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_69a2328f0e848190ac2840eaf2d5ebd2 |
completed | Feb. 28, 2026, 12:10 a.m. |
| NER | Named-entity recognition | batch_69a2346846608190b6b40d31f1dbd685 |
completed | Feb. 28, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69a233c396ec8190986608d07fb251d4 |
completed | Feb. 28, 2026, 12:16 a.m. |
| PDg | Predicate description generation | batch_69a2346794cc8190afce97b703903389 |
completed | Feb. 28, 2026, 12:18 a.m. |
Created at: Feb. 28, 2026, 12:13 a.m.