Triple
T11953183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Will Rogers Boulevard |
E284478
|
entity |
| Predicate | isNamedForOccupationOfHonoree |
P41835
|
FINISHED |
| Object | humorist |
—
|
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: humorist | Statement: [Will Rogers Boulevard, isNamedForOccupationOfHonoree, humorist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNamedForOccupationOfHonoree Context triple: [Will Rogers Boulevard, isNamedForOccupationOfHonoree, humorist]
-
A.
isNamedAfterOccupation
chosen
Indicates that an entity’s name is derived from or based on a particular occupation or profession.
-
B.
isNamedForEponymRole
Indicates that one entity bears a name derived from another entity that serves as its eponym or namesake.
-
C.
isNamedFor
Indicates that one entity bears its name in honor of, or derived from, another entity.
-
D.
hasAwardNamedAfter
Indicates that an entity has an award that is named in honor of another entity.
-
E.
honorificEponym
Indicates that one entity serves as an honorific namesake for another, typically recognizing or commemorating the person or entity in whose honor something is named.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90365da288190a132703df563de23 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.