Triple
T33232366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Retro-Hugo Award |
E850729
|
entity |
| Predicate | maximumYearsBack |
P57614
|
FINISHED |
| Object | 75 years |
—
|
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: 75 years | Statement: [Retro-Hugo Award, maximumYearsBack, 75 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumYearsBack Context triple: [Retro-Hugo Award, maximumYearsBack, 75 years]
-
A.
maximumAgeInYears
Indicates the highest allowable or observed age, expressed in years, associated with an entity or condition.
-
B.
coversYearsTo
Indicates a temporal relationship where one entity spans, includes, or extends up to a specified year or range of years represented by the other entity.
-
C.
totalYearsLimit
chosen
Indicates the maximum total number of years allowed for the relevant activity, condition, or relationship.
-
D.
countsYearsFrom
Indicates a temporal relationship where the number of years is measured starting from a specified reference point or event.
-
E.
durationInYears
Indicates the length of time associated with something, measured in whole or fractional years.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 1, 2026, 1:31 a.m.