Triple
T4063027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A 49 |
E86258
|
entity |
| Predicate | hasSpeedRegulation |
P43145
|
FINISHED |
| Object | regulated speed limits |
—
|
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: regulated speed limits | Statement: [A 49, hasSpeedRegulation, regulated speed limits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpeedRegulation Context triple: [A 49, hasSpeedRegulation, regulated speed limits]
-
A.
hasVariableSpeedLimits
Indicates that the subject is associated with speed limits that can change depending on conditions, time, or location.
-
B.
regulatesSpeedLimitBy
chosen
Indicates that one entity determines, controls, or sets the speed limit applicable to another entity or context.
-
C.
hasSpeedLimit
Indicates that a specified maximum allowable speed is imposed on the associated entity or context.
-
D.
speedLimitCharacteristic
Indicates that an entity has a specific speed limit property or constraint associated with it.
-
E.
hasSlewRateTypical
Indicates that an entity is characterized by a specified typical (nominal) slew rate value.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd0bdea48190805a79515ee92709 |
completed | March 9, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69aef90438908190a005b08ba271eacf |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.