Triple
T1075093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navy Cross |
E23817
|
entity |
| Predicate | mayBeAwardedPosthumously |
P4023
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Navy Cross, mayBeAwardedPosthumously, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeAwardedPosthumously Context triple: [Navy Cross, mayBeAwardedPosthumously, true]
-
A.
canBeAwardedPosthumously
chosen
Indicates that something (such as an honor, title, or award) is eligible to be granted to a person after their death.
-
B.
isPosthumous
Indicates that something occurs, is created, or is conferred after the death of the person to whom it relates.
-
C.
posthumousAwardsSuspendedInYear
Indicates that any posthumous awards were suspended or not granted during a specified year.
-
D.
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.
-
E.
hasAwarded
Indicates that one entity has given or conferred an award to another entity.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b92e480c81909a848b48c196a293 |
completed | March 1, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69a4b73ba8208190be7f3cef8c18689b |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.