Triple
T6321037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alabama State Route 183 |
E141736
|
entity |
| Predicate | speedRegulatedBy |
P43145
|
FINISHED |
| Object | Alabama state traffic laws |
—
|
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: Alabama state traffic laws | Statement: [Alabama State Route 183, speedRegulatedBy, Alabama state traffic laws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speedRegulatedBy Context triple: [Alabama State Route 183, speedRegulatedBy, Alabama state traffic laws]
-
A.
regulatesSpeedLimitBy
chosen
Indicates that one entity determines, controls, or sets the speed limit applicable to another entity or context.
-
B.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
-
C.
speedLimitCharacteristic
Indicates that an entity has a specific speed limit property or constraint associated with it.
-
D.
speed
Indicates the rate at which an entity moves or changes position over time.
-
E.
hasVariableSpeedLimits
Indicates that the subject is associated with speed limits that can change depending on conditions, time, or location.
- 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_69c008d13b8c8190be47d896eb735605 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064c61f008190b316b9ff1023b057 |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e5efc48190861b8266e5b0cc0c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:29 p.m.