Triple
T9838430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LICS Test-of-Time Award |
E239159
|
entity |
| Predicate | typicalTimeLag |
P84192
|
FINISHED |
| Object | at least 10 years after original publication |
—
|
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: at least 10 years after original publication | Statement: [LICS Test-of-Time Award, typicalTimeLag, at least 10 years after original publication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTimeLag Context triple: [LICS Test-of-Time Award, typicalTimeLag, at least 10 years after original publication]
-
A.
typicalTimes
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
-
B.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
C.
laterDuration
Indicates that one event or time interval occurs after another and lasts for a specified duration.
-
D.
intendedResponseTime
Indicates the expected or planned amount of time within which a response should be given or received.
-
E.
typicalPeriod
chosen
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
- 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb34921b881909836ba0f5b42a27b |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:33 p.m.