Triple
T5833819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franklin Delano Roosevelt Memorial |
E129416
|
entity |
| Predicate | honorsOffice |
P51002
|
FINISHED |
| Object | 32nd 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: 32nd President of the United States | Statement: [Franklin Delano Roosevelt Memorial, honorsOffice, 32nd President of the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorsOffice Context triple: [Franklin Delano Roosevelt Memorial, honorsOffice, 32nd President of the United States]
-
A.
honorsRole
chosen
Indicates that one entity formally recognizes and respects the position, title, or role held by another entity.
-
B.
honors
Indicates that one entity shows respect, recognition, or esteem toward another entity, often in a formal or ceremonial way.
-
C.
honoursSystem
Indicates that an entity follows or complies with a particular system of rules, standards, or principles.
-
D.
nameHonors
Indicates that a name is given to honor, commemorate, or pay tribute to a particular entity.
-
E.
honourOf
Indicates that one entity is the source, bearer, or cause of another entity’s honor, prestige, or distinguished recognition.
- 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_69c0084af79c81908af128ccc29983d0 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03341e5888190a5f219b6f92cb161 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:54 p.m.