Triple
T8486842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Retry-After |
E200851
|
entity |
| Predicate | unitForDeltaSeconds |
P18870
|
FINISHED |
| Object | seconds |
—
|
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: seconds | Statement: [Retry-After, unitForDeltaSeconds, seconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unitForDeltaSeconds Context triple: [Retry-After, unitForDeltaSeconds, seconds]
-
A.
timeScaleUnit
chosen
Indicates the unit of temporal measurement (such as seconds, minutes, or hours) used to express a given time scale.
-
B.
timeUnitOfFrequency
Indicates the unit of time (e.g., day, week, month) in which a given frequency is measured or expressed.
-
C.
offsetSeconds
Indicates a temporal relationship where one event or time point occurs a specified number of seconds before or after another reference time.
-
D.
baseUnitsTimeExponent
Indicates the exponent applied to the time dimension in the base units that define a derived physical quantity.
-
E.
unitSystem
Indicates the system of measurement units (such as metric or imperial) that is used to quantify associated values or attributes.
- 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe53c4d608190a766c0e919a4b96f |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:13 p.m.