Triple
T18400423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autopista Central |
E449977
|
entity |
| Predicate | regulatesSpeedBy |
P43145
|
FINISHED |
| Object | posted 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: posted speed limits | Statement: [Autopista Central, regulatesSpeedBy, posted speed limits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesSpeedBy Context triple: [Autopista Central, regulatesSpeedBy, posted speed limits]
-
A.
regulatesSpeedLimitBy
chosen
Indicates that one entity determines, controls, or sets the speed limit applicable to another entity or context.
-
B.
canReduceSpeedTo
Indicates that an entity has the capability to lower its speed to a specified level or threshold.
-
C.
supportsSpeedControls
Indicates that an entity provides or is compatible with mechanisms to adjust or control speed.
-
D.
speedSupervision
Indicates a relationship where an entity monitors, controls, or enforces limits on the speed of another entity or process.
-
E.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e5194f2a8c8190afcd7db23e3795fb |
completed | April 19, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:46 a.m.