Triple
T950776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Hess Award |
E20515
|
entity |
| Predicate | hasPrestige |
P12620
|
FINISHED |
| Object | prestigious honor |
—
|
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: prestigious honor | Statement: [Henry Hess Award, hasPrestige, prestigious honor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrestige Context triple: [Henry Hess Award, hasPrestige, prestigious honor]
-
A.
hasDistinction
chosen
Indicates that one entity possesses, is awarded, or is recognized with a special honor, title, or mark of excellence in relation to another entity or context.
-
B.
hasProminence
Indicates that one entity stands out in importance, visibility, or influence relative to others within a given context.
-
C.
hasAwardLevel
Indicates that an entity possesses or has been assigned a specific level, tier, or rank within an award or recognition system.
-
D.
hadSpecialStatusIn
Indicates that an entity possessed a particular special, exceptional, or non-standard status within a specified context or time period.
-
E.
hasIconicStatus
Indicates that an entity holds a widely recognized, emblematic, or culturally significant status within a particular domain or context.
- 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_69a493b0f2fc81908cd227480a5356a1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3d62e408190855b2883407f6c6b |
completed | March 1, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a045308190ab94f3adab40db8d |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.