Triple
T5156345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Victorian Medal |
E116317
|
entity |
| Predicate | hasPosthumousAwards |
P4023
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Royal Victorian Medal, hasPosthumousAwards, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPosthumousAwards Context triple: [Royal Victorian Medal, hasPosthumousAwards, no]
-
A.
isPosthumousAwardRecipientOf
Indicates that an entity received an award that was granted after their death.
-
B.
posthumousAwardsRestoredInYear
Indicates that awards, previously revoked or unrecognized during a person’s lifetime, were officially reinstated or granted in a specified year after their death.
-
C.
canBeAwardedPosthumously
chosen
Indicates that something (such as an honor, title, or award) is eligible to be granted to a person after their death.
-
D.
posthumousAwardsSuspendedInYear
Indicates that any posthumous awards were suspended or not granted during a specified year.
-
E.
hasMultipleAwardsIndicatedBy
Indicates that an entity is recognized as having received multiple awards, as evidenced or signaled by a specified source or indicator.
- 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_69bd445d94788190b72e2cc563120995 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c1354c81908176703b4853c1a4 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b0fbb88190851e2d7ae1bdcc09 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:44 p.m.