Triple
T5384048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mam Tor |
E113158
|
entity |
| Predicate | roadClosureReason |
P8451
|
FINISHED |
| Object | landslips |
—
|
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: landslips | Statement: [Mam Tor, roadClosureReason, landslips]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadClosureReason Context triple: [Mam Tor, roadClosureReason, landslips]
-
A.
closedToThroughTraffic
Indicates that a route or area is not accessible for general passage and cannot be used as a through route for traffic.
-
B.
roadClosesIn
Indicates that a road becomes closed or inaccessible within a specified location, area, or boundary.
-
C.
hasSpeedRestrictionReason
Indicates the reason or cause for which a speed restriction has been imposed on an entity.
-
D.
closureReason
chosen
Indicates the reason or cause for which an entity, process, or case has been closed or terminated.
-
E.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
- 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_69bd4436a1988190af18dcff7fd306b4 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd86f39edc81908e53973cef1bc0f3 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.