Triple
T16180039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ABS |
E392659
|
entity |
| Predicate | mayNotReduce |
P122017
|
FINISHED |
| Object | stopping distance on loose gravel |
—
|
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: stopping distance on loose gravel | Statement: [ABS, mayNotReduce, stopping distance on loose gravel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayNotReduce Context triple: [ABS, mayNotReduce, stopping distance on loose gravel]
-
A.
mayNot
Indicates that an entity is not permitted or is prohibited from performing a particular action or entering into a specified relationship.
-
B.
mayNotFit
Indicates that one entity is unlikely or not expected to be suitable in size, capacity, or compatibility to be placed into, combined with, or used within another entity or context.
-
C.
mayReject
Indicates that one entity has the authority or option to refuse, decline, or not accept another entity or proposal.
-
D.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
-
E.
mayResultIn
Indicates that one entity has the potential to cause, lead to, or bring about another entity or outcome, without guaranteeing that it will occur.
- F. None of above. chosen
Provenance (4 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2205b88b481908ecdd8d663dc668b |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:02 a.m.