Triple
T20016860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devizes flight of locks |
E494743
|
entity |
| Predicate | requiresTimeToPass |
P17474
|
FINISHED |
| Object | several hours |
—
|
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: several hours | Statement: [Devizes flight of locks, requiresTimeToPass, several hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresTimeToPass Context triple: [Devizes flight of locks, requiresTimeToPass, several hours]
-
A.
airedUntil
Indicates the date or time up to which something, typically a broadcast or series, was shown or transmitted.
-
B.
durationRequirement
Indicates that a specified action, process, or state must persist for at least a certain length of time to satisfy a condition or rule.
-
C.
requiresStartTime
Indicates that an entity cannot be valid, initiated, or executed unless a specific start time has been provided or is in effect.
-
D.
heldUntil
Indicates that a state, condition, or action continues to hold true up to a specified time or event, and may cease to hold immediately after that point.
-
E.
timeToComplete
chosen
Indicates the duration required for an entity or process to be fully completed.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6623cb8188190b95913ffed895930 |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:34 p.m.