Triple
T28996598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Last-Modified |
E736181
|
entity |
| Predicate | mustNotBeInFuture |
P70965
|
FINISHED |
| Object | relative to server time |
—
|
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: relative to server time | Statement: [Last-Modified, mustNotBeInFuture, relative to server time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mustNotBeInFuture Context triple: [Last-Modified, mustNotBeInFuture, relative to server time]
-
A.
meetsInPast
Indicates that two entities encountered or came together at some point in the past.
-
B.
notEarlierThan
chosen
Indicates that one event, time, or state does not occur before another, i.e., it is simultaneous with or later than the referenced point.
-
C.
startDateConstraint
Indicates a restriction or condition placed on when something is allowed to start, typically specifying valid or required start dates.
-
D.
isFutureEvent
Indicates that an event is scheduled to occur at a time later than the present moment.
-
E.
permittedAfterDate
Indicates that an action or condition is allowed to occur only on or after a specified date.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fb6ef4881909a758c3538fdec03 |
completed | May 2, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 9:31 a.m.