Triple
T35740085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forest's Elbow |
E1033008
|
entity |
| Predicate | brakingZone |
P183876
|
FINISHED |
| Object | heavy braking required |
—
|
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: heavy braking required | Statement: [Forest's Elbow, brakingZone, heavy braking required]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brakingZone Context triple: [Forest's Elbow, brakingZone, heavy braking required]
-
A.
hasBrakingZoneFrom
Indicates that an entity has a designated braking zone that originates from or is defined relative to another entity or location.
-
B.
hasBraking
Indicates that an entity possesses or is equipped with a braking capability or braking system.
-
C.
hasBrakingRole
Indicates that an entity participates in a braking process by fulfilling a specific braking-related function or responsibility.
-
D.
brakeFeature
Indicates that an entity possesses or is equipped with a particular braking-related feature or capability.
-
E.
brakeApplication
Indicates that a braking action is being applied to slow down or stop an entity.
- 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_69f76e119d508190a3873cb302063832 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a34e80dc8190980d5b7b0b91341d |
completed | May 3, 2026, 7:34 p.m. |
Created at: May 3, 2026, 4:06 p.m.