Triple
T386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoover Medal |
E7
|
entity |
| Predicate | namedForPosition |
P63
|
FINISHED |
| Object | 31st President of the United States |
—
|
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: 31st President of the United States | Statement: [Hoover Medal, namedForPosition, 31st President of the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForPosition Context triple: [Hoover Medal, namedForPosition, 31st President of the United States]
-
A.
namedAfter
chosen
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
B.
positionHeld
Indicates that an entity occupies or has occupied a specific role, job, office, or position within an organization or context.
-
C.
givenName
Indicates the personal first name assigned to an individual.
-
D.
presentedBy
Indicates that something (such as an event, performance, or work) is formally organized, hosted, or introduced by a particular person or entity.
-
E.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
- 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_69a222a954e48190b48f126a67485661 |
completed | Feb. 27, 2026, 11:03 p.m. |
| NER | Named-entity recognition | batch_69a2304aaa2c8190ab7e8dd5da977c11 |
completed | Feb. 28, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69a22918087081909e717b8bee896e8f |
completed | Feb. 27, 2026, 11:30 p.m. |
Created at: Feb. 27, 2026, 11:04 p.m.